Scenario: it's the end of the world, and the only useful crypto left is bitcoin: it runs on a phone or any computer, and it's a persistent, unfuckable-with record of comms and accounting.
Communities run their own forks: sovereign chains, fresh difficulty (CPU/phone mineable again), no permission needed. Fine. But communities amalgamate, and when they do, they want one merged history of everything that happened, without any chain having to die for it.
This is how: a notarization meta-chain. The chains stay alive; their histories get continuously woven into one merged ledger.
A block header is already a Merkle commitment to a chain's entire history. So merging histories doesn't mean importing transactions; it means recording which block each community's chain was at, when. One 74-byte OP_RETURN per anchor interval. The whole merged ledger is cheap enough for the apocalypse: headers are 80 bytes each (all of BTC's history is about 77 MB), and an SPV proof of any event is a few KB, verifiable on a phone over a mesh link.
community A's chain --+
+--> notary --> anchor (OP_RETURN) --> MERGED LEDGER
community B's chain --+ |
every k-deep block
(anyone can verify with KB-scale proofs)
OP_RETURN | "MRG1" (4B) | chain_id (2B) | height (4B LE) | block_hash (32B) | utxo_muhash (32B)
utxo_muhash is the chain's UTXO-set commitment (gettxoutsetinfo "muhash"):
each anchor pins down both the history and the complete accounting state,
who held what, at that height. That's the "record of comms and accounting",
committed, forever.
Ongoing merge (the steady state). Each community runs a notary: watch your chain, and every k-deep block, anchor it into the merged ledger. New history folds in as time passes. Cross-community ordering exists at each anchor point: a DAG of histories, growing together.
Retroactive amalgamation (a new community joins). They present their header chain from genesis (or a checkpoint); PoW is verified; an admission anchor is recorded. Their entire history, every tx since their genesis, is now part of the merged ledger, provable by anyone. No transactions imported, no balances moved, no chain retired.
Prove any event on any community chain is in the merged history:
- Merkle branch: tx -> its block header (
gettxoutproof) - Header walk: tx block -> anchored block (PoW + prevhash each step)
- Decode the anchor OP_RETURN in the merged ledger; chain_id/height/hash must match
- SPV-proof the anchor tx itself into the merged ledger's headers
A few KB of proofs total. No full node needed to verify. Ever.
- Runs on anything: fresh chains start at trivial difficulty, so CPU/phone mining is viable again; verification is KB-scale.
- Matches social trust: a federation of community reps runs the notaries. Trust was always social; the math just makes the record tamper-evident. When comms are down, chains keep working alone; when comms return, anchors resume and the merged history heals forward.
- Censorship-resistant memory: once anchored, history can't be quietly rewritten: changing one old tx invalidates every header and anchor after it.
- Shared record, not shared money: each community's coins stay sovereign. Cross-chain double-spends of shared-history UTXOs can't be prevented by anchoring; that needs a peg layer (bridge, atomic swaps, or drivechains). Amalgamate the accounting first; the money is a later, harder merge.
- The merged view lags by anchor interval + k confirmations; deeper reorgs are handled socially ("chain left the federation").
- Anchor placement trusts the federation keys; verification of what's anchored is trustless. Upgrade path when civilization reboots: native light-client verification in consensus, or ZK consensus proofs.
anchor.py: MRG1 payload codecnotary.py: the daemon that folds new history into the merged ledgerspv.py: stdlib-only SPV: PoW, header linkage, Core-faithful partial-Merkle-tree traversalverify.py/realverify.py: merged-history membership proofs (regtest + real mainnet)demo.sh: two-community end-to-end demo
Verified: regtest demo PASS (tx buried 6 deep, anchored, SPV-proven); real mainnet PASS (the 2010 pizza tx proven against the real chain; live tip headers verified at full current difficulty). Works against any Core-derived chain unchanged: BTC, BCH, BSV, XEC, DOGE, LTC, or your commune's fork.