Per-Commit
Every individual PoI commit, including mint, burn, reconciliation, resolution, token creation, and max supply update, consumes STRX.
STRX is the settlement token for the StrikeX Tokenisation Engine. Every Proof of Integrity commit and every batch anchor consumes STRX.
STRX settles the protocol cost of the integrity layer that validates, commits, and anchors that execution.
Every individual PoI commit, including mint, burn, reconciliation, resolution, token creation, and max supply update, consumes STRX.
When commits are batched and anchored on-chain as a Merkle root, the batch itself consumes STRX to cover the integrity anchoring.
Consumed STRX is transferred from the provider's vault and burned on-chain.
The Engine validates and executes operations. Proof of Integrity commits and anchors those operations cryptographically. STRX settles the protocol cost of that process on-chain.
In production, these components are coupled. If the engine processes an integrity-bearing operation, the corresponding PoI activity consumes STRX under the configured rules. If the required consumption event is absent, the operation is not treated as a valid production integrity event.
STRX consumed by an integrity event is transferred from the provider's credit vault and burned. Every consumed STRX is permanently removed from circulating supply.
Each PoI commit and batch anchor triggers a corresponding STRX burn. The two events share a settlement reference derived from the PoI hash, so any burn can be matched to the integrity event it settled.
The protocol does not debit one provider's vault for another provider's activity. Vault balances, consumption history, and configuration changes are all publicly readable on-chain.
If a vault does not contain sufficient STRX for a required consumption event, the corresponding production operation fails closed or remains uncommitted until the vault is replenished.
The integrity layer produces proofs that anyone can verify without holding STRX or paying a protocol fee. Producing those proofs has a cost; verifying them does not.
STRX is the protocol token used to account for integrity work in the StrikeX Tokenisation Engine. Proof of Integrity activity consumes STRX and burns it, making integrity a measurable part of the tokenisation stack rather than an invisible operating cost.
Gas pays the blockchain network. STRX accounts for the integrity layer around the transaction. Using STRX keeps that layer separate from chain gas, avoids reliance on third-party stablecoin issuers, and ties integrity consumption directly to the StrikeX protocol.
Yes. Gas pays the underlying blockchain for transaction execution. STRX is consumed by the integrity layer that records and anchors material tokenisation events.
STRX costs are configured at the protocol level and can vary by provider, asset configuration, and operation type. The aim is to make the cost of producing integrity evidence proportionate to the activity being processed.
A credit vault is a provider-scoped STRX allocation used by the protocol to account for that provider's STRX consumption. Provider vaults are separate, so one provider's activity does not debit another provider's allocation.
No, StrikeX manages provider credit vaults at the infrastructure layer, so providers can use the tokenisation stack without operating STRX mechanics themselves.
Provider vaults can be StrikeX-managed, automatically topped up, or supported by an approved overage arrangement depending on the provider agreement. If all configured credit options were exhausted, the issue would be surfaced for operator action before integrity activity continued.
STRX used for Proof of Integrity is 100% burned. The burn amount linked to a PoI event is part of the public record.
Yes. Public verification can show the STRX burned for the relevant Proof of Integrity event alongside the commitment it relates to.
No. Public verification does not require holding STRX or paying a protocol fee.