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 | MERKLEBRANCHVERIFY |
|---|---|
| What the text proposes | BIP 116, MERKLEBRANCHVERIFY. A general approach to bitcoin contracts is to fully enumerate the possible spending conditions and then program verification of these conditions into a single script. |
| Who may write | Mark Friedenbach |
| What is settled | A general approach to bitcoin contracts is to fully enumerate the possible spending conditions and then program verification of these conditions into a single script. |
| 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 |