Protocol specification booklets and an engineering notebook, editorial illustration
BIP 360 / CONSENSUS

A proposed script-only commitment.

Pay-to-Merkle-Root proposes an output format without Taproot’s key-path spending route.

Read the explanation
← All standards

Why it exists

BIP 360 proposes Pay-to-Merkle-Root, or P2MR, an output type that commits directly to a script tree without Taproot’s key-path spend. The aim is to avoid leaving an elliptic-curve output public key exposed while preserving script-tree spending.

How it works

A P2MR output would commit to the root of allowed spending scripts. A spender reveals the selected script and the proof connecting it to that root, then satisfies the script. There is no separate route that spends solely with a signature for an exposed output key.

This distinction targets long-exposure quantum attacks: an attacker with a sufficiently capable future computer would not find a Taproot-style output public key sitting permanently in the output. It does not replace all signature cryptography, and a chosen spending script may reveal conventional public keys when used.

PUT IT IN CONTEXT

A practical example

Consider a hypothetical script tree containing a normal spending branch and a delayed recovery branch. P2MR would require the spender to reveal and satisfy one branch. A coin holder would need the relevant script and tree information in their recovery records; a seed alone would not describe every possible policy.

What to keep in mind

It does not by itself prevent short-exposure attacks against public keys revealed in the mempool. Reusing exposed keys or scripts can undermine the intended protection. The proposal does not establish when quantum attacks become feasible or supply a complete post-quantum signature system.

Status & implementation

The current official title is Pay-to-Merkle-Root (P2MR), version 0.12.1, and its status is Draft. It is a proposed soft fork, not an activated address type. Earlier names and scopes should not be used as its current specification.

Specification status: Draft · Sources checked 13 November 2026

Read the sources

Put the standard in context.

Explore the practical guide

Find your next answer.

Search the complete field guide · Esc to close