Quantum-Safe Bitcoin Migration
Bind your Bitcoin key to a post-quantum ML-DSA-65 signature and require it to spend — an open, runnable toolkit, verified against Bitcoin's official test vectors and proven with a real on-chain Taproot spend.
This isn't a slide deck. Our kit built, signed, and broadcast a real Taproot key-path spend — now confirmed in a block. Every layer is checked against Bitcoin's official BIP-173/340/350/341 test vectors.
Why it matters
A large quantum computer running Shor's algorithm can recover a secp256k1 private key from an exposed public key — putting any Bitcoin with an on-chain pubkey at risk. Migration means binding today's key to a post-quantum successor and requiring a PQC signature to spend, without invalidating already-signed history.
How it works
Bind the keys
Your classical secp256k1/Taproot key is cryptographically bound to a new post-quantum ML-DSA-65 (FIPS-204) key, dual-signed.
Require a post-quantum signature
After migration, spending needs the PQC signature — so an attacker who breaks secp256k1 still cannot move the funds.
Anchor it, verify it
The commitment is anchored first-seen and pinned by every verifier — a rebound forgery is rejected. Anyone can check it offline.
Run it yourself
Open-source and self-verifiable in one command — no signup, no trust required.
$ npx fractal-pqc verify-vector $ npx fractal-pqc selftest $ npx fractal-pqc keygen --taproot > tk.json $ npx fractal-pqc receive --key tk.json --network tb $ npx fractal-pqc send-testnet --key tk.json --to <addr> --amount 20000 --broadcast
Honest scope
The on-chain proof runs on Mutinynet, a public Bitcoin signet with identical consensus rules and Taproot/BIP-341 to mainnet — which is exactly why it proves correctness. This is a reference toolkit (key-path spends), not yet audited and not yet on mainnet. We say precisely what it is.
Build quantum-safe Bitcoin custody
Post-quantum migration, verifiable and open. Explore the tooling behind FractalAI's production post-quantum stack.