Definition: Pay-to-Merkle-Root (P2MR) is a proposed Bitcoin output type described by Draft BIP 360. It commits to a Merkle root of spending scripts while omitting Taproot’s key-path spend. The proposal aims to reduce exposure to certain long-duration quantum attacks on public keys; it is not an activated Bitcoin feature and does not add post-quantum signatures by itself.1
| Type | Proposed SegWit version 2 output type |
|---|---|
| Proposal | BIP 360 — Pay-to-Merkle-Root |
| Status | Draft; not activated on Bitcoin mainnet1 |
| Proposed address format | Witness version 2; mainnet example prefix bc1z; Bech32m encoding1 |
| Directories | Bitcoin Directory · Bitcoin Technology & Infrastructure |
In-Depth Explanation
Bitcoin outputs lock value to conditions that a later transaction must satisfy. Taproot (P2TR), deployed through BIP 341, uses a SegWit version 1 output and supports both a key-path spend and script-path spends. A key-path spend uses a public key commitment; a script-path spend can reveal and execute one selected script from a committed tree, while leaving unused branches undisclosed.2
BIP 360 proposes a different output commitment. A P2MR output contains a SegWit version 2 witness program holding a 32-byte Merkle root. It leaves out the internal key and Taproot key tweak, so there is no key-path spend. Spending would rely on a script path that proves a script belongs to the committed tree. The draft describes mainnet addresses beginning with bc1z and applies Bech32m encoding for witness versions above zero.13
Why remove the key path?
A sufficiently capable quantum computer could use a revealed elliptic-curve public key to attack the corresponding private key. BIP 360 focuses on long-exposure risk: a P2MR output commits to a script tree rather than publishing a Taproot output key in the output itself. That can reduce the time a public key is exposed before a spend. It does not make Bitcoin quantum-proof. Spending a script can reveal public keys inside that script, key reuse can expose keys elsewhere, and a fast attack during transaction confirmation remains outside the proposal’s long-exposure protection.1
Trade-offs and limitations
P2MR is not simply a safer version of every existing Bitcoin address. Removing the key path changes what wallets and applications must construct and sign, and it may remove the convenience or efficiency of a key-path spend. Existing wallets, exchanges, and nodes would need compatible software before they could create or spend such outputs. The draft does not activate a soft fork, guarantee user adoption, or introduce a post-quantum signature algorithm. Its details may change while it remains under review.1
Address encodings also signal a proposal’s status carefully. BIP 350 defines Bech32m for SegWit witness versions 1 and higher, but an encoding alone does not make a new witness version valid under Bitcoin’s active consensus rules. BIP 360 would require network-level consensus changes and supporting wallet and node implementations before users could rely on P2MR on mainnet.3
History
- December 18, 2024: BIP 360 was assigned in the Bitcoin BIPs repository.1
- February 10, 2026: The draft was renamed from Pay-to-Tapscript-Hash to Pay-to-Merkle-Root (P2MR).1
- July 24, 2026: The BIP changelog records version 0.12.1; the proposal remained in Draft status when checked on November 13, 2026.1
Last updated: November 13, 2026.
Related Terms
Related Articles
- What Happens to Bitcoin Mining Rewards After New BTC Issuance Ends?
- Bitcoin as Collateral: Bank Loans, Mortgages, and DeFi Explained
- Why Bitcoin Can Move With Stocks — and Why Correlation Changes
- What the 2024 U.S. Spot Bitcoin ETP Launch Changed — and What It Didn’t
See Also
Sources
- Beast, Hunter, Ethan Heilman, and Isabel Foxen Duke. “BIP 360: Pay-to-Merkle-Root (P2MR).” Bitcoin Improvement Proposals. Accessed November 13, 2026. https://github.com/bitcoin/bips/blob/master/bip-0360.mediawiki.
- Wuille, Pieter, Jonas Nick, and Anthony Towns. “BIP 341: Taproot: SegWit Version 1 Spending Rules.” Bitcoin Improvement Proposals. Accessed November 13, 2026. https://github.com/bitcoin/bips/blob/master/bip-0341.mediawiki.
- Wuille, Pieter. “BIP 350: Bech32m Format for v1+ Witness Addresses.” Bitcoin Improvement Proposals. Accessed November 13, 2026. https://github.com/bitcoin/bips/blob/master/bip-0350.mediawiki.