Bitcoin Quantum Resistance: BIP 360 and BIP 361 Explained

What does BIP 360 change about Bitcoin quantum resistance?

BIP 360 proposes Pay-to-Merkle-Root, a Bitcoin output that commits to a script-tree root without Taproot's key-path spending route. Its intended benefit is to reduce long-duration exposure to elliptic-curve key-recovery attacks. BIP 360 does not itself introduce post-quantum signatures. The source was Draft when checked on September 21, 2026.

Editorial synthesis. Same-release SYNX synthesis; source context: Existing SYNX Bitcoin research and underlying source register.

Le existing Bitcoin research and source register distinguish persistent public-key exposure from the information revealed during spending. Reducing the first does not establish that the spending signature remains safe after its key becomes visible. Short-exposure protection requires further analysis of the signature rules.

Does BIP 361 set a deadline to move Bitcoin?

BIP 361 is a draft migration proposal, not an active deadline for Bitcoin holders. It describes future restrictions on funding quantum-vulnerable outputs and later spending under legacy ECDSA or Schnorr rules. The proposal depends on a future post-quantum-signature BIP. Any timetable must be read together with its activation conditions, unresolved dependencies and the rules actually enforced by the network.

Editorial synthesis. Same-release SYNX synthesis; source context: Existing SYNX Bitcoin research and underlying source register.

At the September 21, 2026 check, existing Bitcoin research and source register is marked Draft and Informational, with a future post-quantum-signature proposal still required. Repository publication, assignment of a BIP number and a software experiment are different from consensus deployment; the proposal alone establishes no active wallet deadline.

Why does Bitcoin migration require more than a new signature?

Bitcoin migration joins three separate tasks: defining secure spending rules, deploying compatible validation and signing software, and giving existing holders a workable transition. Signature size, verification cost, recovery support and service compatibility affect that transition. Choosing a cryptographic algorithm alone does not resolve how inactive holdings, old devices or outputs using legacy authorization rules will be handled.

Editorial synthesis. Same-release SYNX synthesis; source context: Existing SYNX Bitcoin research and underlying source register · SYNX whitepaper — project claims, reviewed September 21, 2026.

The table organizes the distinct roles described in existing Bitcoin research and source register et existing Bitcoin research and source register: output design, signature rules and migration policy.

Migration also creates hard questions about inactive or inaccessible holdings. An upgrade cannot assume every owner still has the keys, follows announcements or can act promptly. A complete proposal needs to describe the consequences for those cases rather than count all funds as migrated when code is published.

New signatures can change transaction size and verification work. The design must address resource costs as well as mathematical security. A scheme standardized for one use is not automatically a drop-in replacement for every blockchain workload.

How do native post-quantum coins differ from a Bitcoin upgrade?

A separate network can adopt different cryptographic rules without migrating Bitcoin's existing outputs. That design freedom does not transfer its protection to BTC or prove the new network's implementation correct. Compare the asset, consensus rules, software and recovery model together.

SynergyX specifies SPHINCS+-SHAKE-128s for SYNX signatures. Its wallet is for its own network. To evaluate that distinction, compare how native post-quantum networks avoid migrating Bitcoin outputs, then review how to separate cryptographic claims from deployment evidence.

How genesis-native signatures differ from Bitcoin migration.

Why signature parameters and migration rules must be evaluated together.

Why post-quantum communication does not replace spending authorization.

How can a holder verify a Bitcoin quantum-upgrade claim?

Verify a Bitcoin quantum-upgrade claim against four items: the proposal's current status, the exact network, the released software that implements it, and evidence that the required rules are active. Then check whether the holder's output type, signing device and recovery method are supported. A repository document, testnet transaction or separate fork does not by itself prove protection for Bitcoin mainnet holdings.

• Document status: draft, implementation, test environment or activated mainnet rule.
• Network identity: Bitcoin mainnet, a test network, a separate fork or another asset.
• Software identity: official release, exact version and supported transaction type.
• Recovery and compatibility: whether backups, services and signing devices support the intended operation.
• Evidence: activation notices and current source documents, rather than a promotional claim that a proposal is already live.

The status checklist records how to distinguish a Bitcoin proposal from an activated migration before treating a claim as current holder guidance.