BIP 361 Post-Quantum Migration Proposal: This guide explains BIP 361 Post Quantum Migration and Legacy Signature Sunset in plain English. It covers the problem behind the BIP, why it matters and whether the proposal is part of Bitcoin today.
TL;DR
- What it is: BIP 361 is a Draft informational consensus-layer proposal describing a possible migration after a separate post-quantum output type exists. It proposes first preventing new funds from being sent to quantum-vulnerable scripts, then later restricting legacy ECDSA and Schnorr spends behind a quantum-safe rescue mechanism.
- Why it matters: BIP 361 is a roadmap proposal for a severe future risk, not an instruction to move funds today. Useful preparation is an accurate custody and script inventory plus adaptable signing architecture while research and consensus remain unresolved.
- Current position: BIP 361 is a Draft informational consensus-layer proposal describing a possible migration after a separate post-quantum output type exists.
BIP 361 Post-Quantum Migration Proposal in simple English
BIP 361 Post-Quantum Migration Proposal: The proposal would permit migration from legacy scripts to post-quantum scripts while disallowing new outputs to vulnerable types after 160,000 blocks, described as roughly three years after activation.
Simple example
A node operator is checking BIP 361 Post-Quantum Migration Proposal. BIP 361 is Draft and Informational and explicitly requires a still-to-be-defined post-quantum signature BIP.
Key terms in plain English
- BIP:
- Bitcoin Improvement Proposal: a document describing a proposed rule, standard or process. Its status must be checked separately.
- Consensus:
- The shared rules full nodes use to decide whether blocks and transactions are valid.
- Node:
- A computer running Bitcoin software that checks data and communicates with other peers.
Status and prerequisite
BIP 361 is Draft and Informational and explicitly requires a still-to-be-defined post-quantum signature BIP. Its dates and phases are proposals, not scheduled network events.
Phase A
The proposal would permit migration from legacy scripts to post-quantum scripts while disallowing new outputs to vulnerable types after 160,000 blocks, described as roughly three years after activation.
Phase B
Two years later at a predetermined height, nodes would tighten verification for ECDSA and Schnorr spends and require a quantum-safe rescue protocol intended to distinguish authentic holders.
Rescue uncertainty
The document discusses hardened BIP32 parent knowledge, zero-knowledge proofs and commit-reveal designs as possibilities. Coverage, efficiency and exact consensus rules are unresolved.
Operational inventory
Custodians can prepare without claiming activation by inventorying script types, exposed public keys, address reuse, signer capabilities, cold-storage access times and migration dependencies.
Governance and custody
A signature sunset could make some coins harder or impossible to spend and creates distribution, coordination and fiduciary questions. Scenario planning must include stakeholder review and reversible testing.
Safe communication
Separate quantum capability estimates, proposal assumptions and deployed facts. Never create urgency-driven transfers, request seed material or imply a deadline before consensus and wallet support exist. Build a revision-pinned evidence pack on an isolated node, wallet or protocol harness.
Frequently asked questions
What is the main point of BIP 361 Post-Quantum Migration Proposal?
BIP 361 Post-Quantum Migration Proposal: The proposal would permit migration from legacy scripts to post-quantum scripts while disallowing new outputs to vulnerable types after 160,000 blocks, described as roughly three years after activation.
For BIP 361 Post-Quantum Migration Proposal, what should a beginner know about status and prerequisite?
BIP 361 is Draft and Informational and explicitly requires a still-to-be-defined post-quantum signature BIP.
For BIP 361 Post-Quantum Migration Proposal, what should a beginner know about phase A?
The proposal would permit migration from legacy scripts to post-quantum scripts while disallowing new outputs to vulnerable types after 160,000 blocks, described as roughly three years after activation.
For BIP 361 Post-Quantum Migration Proposal, what should a beginner know about phase B?
Two years later at a predetermined height, nodes would tighten verification for ECDSA and Schnorr spends and require a quantum-safe rescue protocol intended to distinguish authentic holders.
Conclusion
BIP 361 is a roadmap proposal for a severe future risk, not an instruction to move funds today. Useful preparation is an accurate custody and script inventory plus adaptable signing architecture while research and consensus remain unresolved.
Primary sources
Check the current specification status and the documentation for the exact implementation you operate before moving production funds or changing a mining node.
Join the ASIC Mining Discussion
Members can read and join the discussion
Log in to read comments from other miners. Create a free account if you would like to ask a question or share your experience.
Membership helps us protect the discussion from spam and keep answers useful.