Public methodology

Words should match state.

A transaction going somewhere inaccessible is not automatically a supply burn. ROKO Burn reports the narrower claim that finalized chain evidence supports.

Evidence classes

native-supply-burn

Native supply burn

ROKO issuance decreases by the finalized burned amount.

token-supply-burn

Token supply burn

The verified token total supply decreases by the finalized burned amount.

wrapper-redemption

Wrapper redemption

Wrapper supply decreases while backing is returned; native ROKO is not burned.

claim-destruction

Claim destruction

A pool or protocol claim is destroyed; underlying reserves are not necessarily burned.

sink-retirement

Sink retirement

Assets become inaccessible at a published sink, but reported total supply does not decrease.

When a record becomes public

The transaction and expected mechanism event are observed through Blockscout.
The block number and hash are checked against the ROKO RPC.
The record waits for the configured confirmation depth and canonical-block recheck.
Supply or issuance deltas are reconciled when the mechanism claims a true supply burn.
Only then can the record contribute to finalized totals.

Wallet safety

The browser asks for an account only after you start the composer. It checks chain ID 52370, parses the exact integer amount, simulates the exact call, and binds the review to the account, network, asset, amount, and a short expiration. Any change invalidates the simulation.

Activation status

The native ROKO supply-burn path is active on testnet at the reviewed precompile address 0x0000000000000000000000000000000000000800. Runtime spec 283 finalized at block 82,821. A 0.01 ROKO canary finalized at block 82,920 with a canonical NativeBurned event and an issuance decrease equal to the burn amount plus the separately accounted transaction fee.