Compare
Four documents, the same five questions.
No throughput league table and no yield. The cells are what this library is willing to say about the text.
| Question | Pay-to-Merkle-Root (P2MR) |
|---|---|
| What the text proposes | BIP 360, Pay-to-Merkle-Root (P2MR). We define the Pay-to-Merkle-Root (P2MR) output structure as follows: A P2MR output is similar to a P2TR output (as defined in [[bip-0341.mediawiki|BIP 341]]); however, unlike P2TR outputs, we disable the key path spend for the benefit of quantum resistance by omitting the internal key and the tap tweak step. |
| Who may write | Hunter Beast |
| What is settled | We define the Pay-to-Merkle-Root (P2MR) output structure as follows: A P2MR output is similar to a P2TR output (as defined in [[bip-0341.mediawiki|BIP 341]]); however, unlike P2TR outputs, we disable the key path spend for the benefit of quantum resistance by omitting the internal key and the tap tweak step. |
| Load-bearing assumption | A soft fork does not bind a node that never upgrades. It binds the nodes that enforce the new rejection. |
| What this library says afterwards | Status in the source: Draft. A reading of the public specification, not a copy of it and not a certification. |
| Rights | Official external source only |