Related · tier-1 reading. For what a portable artifact actually is, see Portable Artifact.
Moving assets from chain to chain is a big topic in RWAs and tokenization. Once you separate the asset from the evidence, most of the migration work disappears.
Imagine a fund, company, or government spends five years operating on a blockchain. Over that time, the stuff that accumulates is enormous: tokenized real-world assets, audit trails, AI decisions, ownership records, governance actions, operational history.
Then things break. Cryptography ages. Fees rise. Performance lags. A better chain emerges. With quantum on the horizon, the chain you trusted yesterday may not be the chain you can trust in five years. That blockchain is now a liability and it is time to leave it.
Migration typically means rebuilding infrastructure, reissuing assets on the new chain, and figuring out how to preserve years of history. The last part is usually the hardest, and most projects either skip it or accept that the new chain inherits no provenance from the old one.
The asset moves. The token contract on the old chain is replaced by a new token contract on the new chain. That is normal blockchain work, and it is unavoidable.
The evidence does not move. Every proof that was ever produced — one for every approval, transfer, compliance check, governance action, AI decision — continues to exist independently. It was never the chain's record. The chain only held an anchor pointing to it. Add a new anchor on the new chain for the entire historical record at once (or multiple anchors in any way you want) and you are done.
When the cryptography that secured the old chain breaks, the post-quantum evidence anchored to it does not break with it. Each proof is signed under a three-family post-quantum scheme (ML-DSA-65, FALCON-512, SLH-DSA-128f). The chain is compromised. The proof is post-quantum. Re-anchor on a chain whose signature scheme you still trust and continue.
The disciplined operational pattern uses batched anchoring. You compute a single cryptographic commitment over the receipts you want re-anchored. Could be all of them at once. Could be by year. Could be by asset. Could be a continuous rolling batch. You post that commitment in one transaction on the new chain. Verifying any individual receipt requires the receipt plus a short proof that it belongs to the commitment.
This is the same pattern that has anchored hundreds of millions of timestamps to Bitcoin since 2016 (OpenTimestamps), applied to operational evidence and extended with post-quantum signatures. One transaction on the new chain can anchor an entire historical corpus.
Chain migration is a problem because the chain has been treated as the place where evidence lives. Once evidence is treated as a first-class object that exists independently, the chain becomes infrastructure. Migration becomes a routine operational event, not an existential project.
If the evidence is not chain-dependent, the blockchain becomes replaceable.
Stated precisely: what differs between blockchains are their operational and integration characteristics — fees, performance, cryptographic posture, jurisdiction. 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.
H33-74 produces and anchors the portable proof primitive that makes chain migration a non-event for evidence. It 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).
Read the next concept: how to operate before you have picked a chain at all.
Start Without a Chain H33-74 Overview