Related · tier-1 reading. For what a portable artifact actually is, see Portable Artifact.
If moving evidence between chains requires migration, the evidence was attached to the wrong thing. Chain portability is the property of evidence that does not migrate because it was never bound to a chain in the first place.
For ten years, blockchain attestation has been treated as a chain feature. You pick a chain. You attest on it. Everything you attest lives there. If you ever need to move, you have a migration problem.
Chain portability rejects that model. The receipt is the evidence. The chain is one of many optional notarization surfaces. Moving between chains is not a migration; it is adding a new notarization while the receipt stays exactly the same.
Chain portability is a property of a piece of evidence, not a feature of a chain.
An evidence object is chain-portable if it satisfies three conditions:
An H33-74 receipt is chain-portable by construction. A standard EAS attestation is not. An OpenTimestamps timestamp is partially chain-portable in the sense that the receipt can exist before Bitcoin confirmation, but it is permanently bound to Bitcoin for verification. An OP_RETURN commitment is not chain-portable in any sense.
Evidence outlives the chain it was anchored to. If the chain is deprecated, replaced, exploited, or breaks under quantum attacks, the chain-portable evidence remains verifiable through other anchors or through cryptographic self-verification.
You can choose where to anchor based on what each chain is good at: Bitcoin for institutional durability, Solana for high throughput, Polygon zkEVM for EVM compatibility with L1 security, Zcash for privacy-preserving notarization. The choice is not architectural; it is operational and can change over time.
If the chain you currently use becomes inappropriate, you add an anchor on the new chain and continue operating. The historical evidence does not have to be reconstructed because it was never on the old chain in any sense that bound it there. The chain only held a notarization pointer.
An auditor verifying chain-portable evidence does not need the operator's infrastructure to be running. The receipt, the public keys, and the open-source verifier are sufficient. The evidence layer is decoupled from the operator's continued existence.
The fund's tokenization layer migrates: the ERC-20 token contract is wound down, a new Solana SPL token is issued, and balance reconstruction follows standard tokenization migration. The fund's chain-portable evidence — millions of approvals, transfers, compliance checks, NAV calculations, and governance actions, each one a separate proof does not migrate. It carries forward into the new operation unchanged. The fund posts one new anchor on Solana covering the historical corpus and continues operating with new receipts anchored to Solana directly.
A bank running an internal AI compliance system anchors decision receipts to a public chain for independent timestamping. Five years in, that chain is sunset by its issuer. The proofs of every decision, action, and outcome produced during those five years remain chain-portable. The bank's auditor can verify any of them using only the receipts and the public verifier; the deprecated chain's continued existence is not required. If the bank wants additional independent notarization going forward, it picks a different chain and anchors there.
A regulated fund operates across the US, EU, and UK. Each jurisdiction's auditors prefer different chains for independent verification. The same proofs of every approval, transfer, and compliance event are anchored on all three chains in parallel. The US auditor verifies via Bitcoin. The EU auditor verifies via Ethereum. The UK auditor verifies via Polygon zkEVM. Three audit teams. Three chains. One receipt. No bridges. No cross-chain messaging.
Bridging moves the same asset between chains. The asset is on one chain at a time. Chain portability does not move anything; the receipt exists outside any chain and accumulates notarizations on multiple chains in parallel.
Multi-chain compatibility usually means the same smart contract runs on multiple EVM chains. Chain portability does not require EVM and does not require smart contracts. It works on EVM chains, on Bitcoin, on Solana, on Zcash, and on any chain that can hold a 32-byte commitment.
Many systems advertise themselves as chain-agnostic. Usually that means the system supports multiple chains as alternative deployment targets, but each deployment is single-chain. Chain portability is stronger: the same evidence exists across all anchored chains simultaneously, and the receipt is not tied to any of them.
What differs between blockchains are their operational and integration characteristics: durability profile, throughput, privacy, EVM compatibility, jurisdictional standing. The H33-74 primitive and its cryptographic properties remain unchanged. Migrating from one blockchain to another changes the anchoring substrate and deployment environment. It does not change the H33-74 primitive, the cryptographic evidence, or the verification model. That is precisely what makes the evidence chain-portable rather than chain-bound.
H33-74 produces and anchors the portable proof primitive; chain portability is a property of that primitive. H33-74 does not monitor systems for control drift (that is HATS), it does not render the pass/fail verdict on an attestation (an independent verifier does — see Verification), and it does not govern agents or preserve decision authority (that is Agent-008).
Categories in software get created when a property becomes valuable enough to compare every system against. Containers became a category once portability across infrastructure became more valuable than each OS's native packaging. Object storage became a category once durability across hardware generations became more valuable than each filesystem's structure.
Chain portability is the same kind of property. Once institutions start operating long enough to outlast individual chains (which is now the realistic time horizon for regulated treasury, AI governance, tokenization, and operational compliance), the property of evidence-that-outlives-the-chain becomes more valuable than any individual chain's features.
At that point, the question stops being "which chain do you attest on?" and becomes "is your evidence chain-portable?" Some attestation systems are portable. Others are tied to the infrastructure that created them. Both have legitimate use cases. The portable systems gain a structural advantage as institutional time horizons extend beyond any single chain.
Six pages explaining what chain portability means, why migration becomes irrelevant, and how the mechanism actually works.
Why Chain Migration Shouldn't Exist Mint Once. Anchor Anywhere.