One proof of a single treasury authorization. Polygon zkEVM anchor shipping first. Bitcoin and Ethereum anchors next. The receipt does not change as the anchor set grows.
The fastest way to understand chain portability is to walk through the receipt and its anchors. What follows is a worked example using the same wire format the H33 substrate produces in production.
A computation runs. In this example: a treasury policy engine authorizes a 5,000,000 USDC transfer from Treasury Wallet A to Treasury Wallet B, under policy treasury-v3.2, approved by signer jane.cfo@h33.ai with secondary approval from controls.bot.
The H33 substrate produces a 74-byte receipt:
At this point the receipt exists and is verifiable. No chain has been touched. Any third party with the public keys and the open-source verifier can confirm the three PQ signatures match the receipt content.
The treasury team posts the receipt's commitment to Polygon zkEVM mainnet. One EIP-1559 transaction. Calldata contains the 32-byte commitment.
This is the first chain we are shipping. The Bitcoin and Ethereum anchors land in subsequent backend releases (status below).
The receipt now has one independent anchor. The receipt itself is unchanged. Its 74 bytes are exactly the same as in Step 1.
The same receipt will accumulate independent anchors on Bitcoin and Ethereum mainnet in subsequent backend releases. Bitcoin anchoring uses Taproot (with OP_RETURN as a documented fallback). Ethereum mainnet anchoring uses an EIP-1559 calldata commitment. Both anchors are independent: each can fail or be added later without affecting the others.
The verifier widget already polls public chain explorer endpoints for these rows. Once real transaction hashes replace the placeholders, the same widget shows live confirmation status without code changes.
The treasury team in this example has not committed to any single chain. They have anchored where each audience prefers verification. If Polygon zkEVM becomes inappropriate in two years (regulatory change, cryptographic concern, performance issue), the team removes Polygon from new anchors and continues with Bitcoin and Ethereum. The historical receipts already anchored to Polygon do not need to be moved; their Bitcoin and Ethereum anchors continue verifying them.
If the audit horizon extends 10 years and Ethereum's signature scheme has been replaced with a post-quantum scheme, the H33-74 receipt's own PQ signatures still verify because they were never coupled to Ethereum's signatures.
Nothing moved between chains. Each anchor is an independent commitment of the same receipt.
No chain talks to any other chain. Each anchor is a standalone transaction on its own chain.
There is no "primary" anchor and "replicas". All three anchors are equal-rank independent notarizations.
The mechanism that makes one-receipt-many-chains possible is chain portability.
Chain Portability One Receipt. Multiple Chains.