STRX: the economics of integrity.
What STRX does
STRX is the settlement token for the StrikeX Tokenisation Engine. Every Proof of Integrity commit and every batch anchor consumes STRX from the provider’s on-chain credit vault, and the consumed STRX is burned.
This consumption is charged in addition to the gas cost of the underlying on-chain transaction. Gas pays for chain execution. STRX settles the protocol cost of the integrity layer that validates, commits and anchors that execution.
How STRX is consumed
Consumption happens at two levels.
Per-commit. Every individual PoI commit, whether it records a mint, burn, reconciliation, resolution, token creation or max supply update, consumes STRX.
Per-batch. When commits are batched and anchored on-chain as a Merkle root, the batch itself consumes STRX to cover the integrity anchoring.
Costs are configurable per asset, per provider and per operation type, set at the protocol level by StrikeX. A commit anchoring a complex institutional issuance should not necessarily cost the same as one anchoring a test instrument, because the evidence burden, operating controls and integrity requirements may be different. A mint may be weighted differently from a reconciliation commit.
Configuration changes are recorded on-chain and observable. Because consumed STRX is burned, changes in configured cost affect burn volume rather than a StrikeX revenue balance.
The granularity matters as on-chain execution costs continue to fall. If integrity commits were too cheap, an attacker or misconfigured integration could flood the integrity chain with high volumes of low-value activity, making replay and verification expensive for everyone. Configurable STRX costs make that economically impractical.
One token, every chain
The Tokenisation Engine is multi-chain, with deployments across Ethereum, Arbitrum and BNB Chain. STRX provides a single settlement layer for the integrity component across supported networks. The cost of a PoI commit or batch anchor is denominated in STRX whether the related activity occurs on Ethereum, Arbitrum, BNB Chain or another supported chain.
Providers do not need a separate integrity settlement model for each network. Gas costs may still vary by chain, but the protocol cost of the integrity layer is accounted for consistently in STRX. Because STRX is native to the StrikeX economic model, the integrity settlement layer does not depend on an external token issuer for this component of protocol settlement, though normal blockchain, smart contract and operational risks still apply.
Credit vaults
Each provider has a dedicated provider-scoped STRX credit vault on-chain. The engine tracks vault balances as part of its settlement process and deducts STRX as operations are committed and anchored.
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 should fail closed or remain uncommitted until the vault is replenished.
What happens to consumed STRX
STRX consumed through PoI commits and batch anchors is transferred from the provider’s credit vault and burned. Every STRX consumed by an integrity event is permanently removed from circulating supply.
Each PoI commit and batch anchor triggers a corresponding STRX burn. The integrity event is the authoritative record of what happened — the operation type, supporting evidence, rule version and place in the integrity chain — and the burn is the on-chain settlement of its protocol cost. The two events share a deterministic settlement reference derived from the PoI hash, so a burn can be matched to the integrity event it settled, and an integrity event can be matched to the burn that settled it, by anyone inspecting the public record. Consumption volumes and per-provider breakdowns are on-chain data, subject to the same standard of public auditability as the integrity layer itself.
How it connects
The Tokenisation 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 the production model, 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 STRX consumption event is absent, the operation should not be treated as a valid production integrity event.
The integrity layer produces proofs that anyone can verify without holding STRX or paying a protocol fee. Producing those proofs has a cost, and that cost is settled in STRX, burned on-chain from auditable provider vaults.
The verifier pays nothing. The provider’s activity drives the integrity work. STRX is the layer where that work is accounted for and permanently removed from supply.