Signatures authorize spends; hashing serves other roles

Bitcoin transactions spend previously created unspent transaction outputs, or UTXOs. The output conditions determine what a later spend must demonstrate. Traditional signature paths use ECDSA, while BIP 340 specifies Schnorr signatures over the same secp256k1 curve for the Taproot system. Schnorr improves important properties, but it is not a post-quantum signature scheme.

A sufficiently capable quantum computer threatens the elliptic-curve discrete-logarithm assumption behind both. This is distinct from discussing SHA-256 proof of work or the hashes used in addresses. Saying that Bitcoin uses a strong hash does not answer whether an exposed signing public key can resist quantum key recovery. The roles must be kept separate when describing either threats or proposed fixes.

Sources:Bitcoin developer guide: transactionsBIP 340: Schnorr signatures for secp256k1BIP 360: Pay-to-Merkle-Root

Exposure depends on the output and its history

Some output types publish a public key before a spend; others initially publish a hash commitment and reveal the key when spending. Taproot outputs expose an output public key. Reusing a key can also leave funds controlled by public material that was revealed in an earlier transaction. A balance alone therefore cannot describe the relevant exposure.

Hash commitments can reduce a long exposure window, but they do not automatically solve an attack during transaction propagation and confirmation. The distinction is between an attacker having substantial time with an already exposed key and an attacker trying to recover it after a pending spend reveals it. Any numerical exposure estimate must state its output classifications, reuse assumptions, data date, and treatment of shared keys.

Sources:Bitcoin developer guide: transactionsBIP 341: Taproot spending rulesBIP 360: Pay-to-Merkle-Root

BIP 360 proposes P2MR, not an activated universal fix

The reviewed BIP 360 is titled Pay-to-Merkle-Root, or P2MR, and has Draft status. It proposes an output resembling Taproot script trees with the key-path spending route removed. By committing to the script-tree root rather than publishing a directly spendable elliptic-curve output key, the proposal targets long-exposure risks in that construction.

The BIP explicitly distinguishes this from protection against short-exposure attacks, which may require post-quantum signatures. It does not justify describing Bitcoin as already quantum-resistant. A reader should track specification revisions, implementation work, consensus discussion, and eventual activation evidence separately. A BIP number establishes an identifiable proposal, not agreement by every participant or deployment on mainnet.

Sources:BIP 360: Pay-to-Merkle-Root

Existing funds introduce a separate coordination problem

Even if a new post-quantum spending path is accepted, owners must migrate existing holdings and supporting software must recognize it. Wallets, hardware signers, exchanges, custodians, and transaction-building systems all participate in that transition. Dormant funds and already exposed public keys create questions that a new signature verification rule alone cannot settle.

BIP 361 discusses a possible migration and legacy-signature sunset framework. The reviewed text is an informational draft, with dependencies and unresolved design questions. Its suggested phases and time horizons are proposal terms, not a live deadline for Bitcoin users. Coverage should explain the trade-offs and current status without converting an author proposal into an adopted network policy.

Sources:BIP 361: Post Quantum Migration and Legacy Signature Sunset

Track readiness through concrete artifacts

A useful progress record connects a specification revision to implementation, tests, audits, interoperability, and any activation mechanism. It should identify signature parameters, transaction size implications, validation cost, and wallet recovery behavior. Testnet demonstrations and source-code support are meaningful milestones, but they answer different questions from mainnet acceptance and broad user adoption.

This article has not scanned current UTXOs or independently measured activation. It provides a map of the primary documents and the distinctions needed to read them. Future updates should preserve those boundaries, link the exact proposal version, and record what changed. Avoid fixed Q-day countdowns or claims that ordinary address practices alone supply a complete post-quantum migration.

Sources:BIP 360: Pay-to-Merkle-RootBIP 361: Post Quantum Migration and Legacy Signature SunsetBIP 340: Schnorr signatures for secp256k1