Why "the same bytes" is a structural property, not a marketing claim
The commit is the SHA3-256 of asset ∥ authority ∥ timestamp ∥ policy_state. The inputs are the same regardless of which chain anchors the output. So the output — the 32-byte commit — is the same too. That's not a property of the chain; it's a property of the math.
This is why "one receipt, multiple chains" is operationally true and not just a slogan. Anchor on Solana, then anchor on Bitcoin via Taproot, then anchor on Ethereum. The bytes on each chain are identical. The verification against each chain independently produces the same identity object.
How each chain carries it
- Bitcoin — Taproot (BIP-341). The commitment is embedded in an x-only tweaked public key, producing a normal spendable P2TR output. Indistinguishable from any other Taproot UTXO on-chain. No data-carrier baggage, no soft-fork relitigation.
- Solana — memo program. The commitment lives in a program-derived address backed by the memo or a custom program. Sub-second finality.
- Ethereum & EVM L2s. The commitment lives in calldata or as an indexed event topic. Standard infrastructure; works the same on Ethereum mainnet, Arbitrum, Base, Optimism, Polygon, Avalanche.
- Polygon zkEVM. STARK-backed privacy path — the commitment is part of a verifiable computation circuit rather than a public log entry.
- Zcash. Embedded as a unique nullifier in a shielded transaction.
Each chain stores 32 bytes natively. None of them need to know about the others. The receipt is the cross-chain coordinator; the chains are the publishing layer.
No bridge required
Bridges exist because the asset's identity is normally chain-bound. To move the asset from Chain A to Chain B, you have to create a representation on Chain B and trust that the bridge correctly mirrors the asset's state.
With a portable 32-byte identity, there's no asset to move. The identity is the same on every chain that anchors it. Anchoring a second chain isn't a transfer — it's a publication. No counterparty, no custodian, no bridge-operator risk.
What this enables for institutional buyers
"What chain are you on?" stops being the right question. The right question becomes "what's the redundancy of your anchoring?" An asset anchored on Bitcoin and Solana and Ethereum has three independent finality guarantees. The asset doesn't need any one of them to survive — only one.
That's institutional continuity at the chain layer. And it's why we lead with chain portability when talking to allocators — it's the only architectural answer to long-term chain risk that doesn't involve picking a winner.