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 | OP_CHECKCONTRACTVERIFY |
|---|---|
| What the text proposes | BIP 443, OP_CHECKCONTRACTVERIFY. To add consensus support for a new tapscript opcode that enables a new type of output restrictions: OP_CHECKCONTRACTVERIFY ( OP_CCV ). |
| Who may write | Salvatore Ingala |
| What is settled | To add consensus support for a new tapscript opcode that enables a new type of output restrictions: OP_CHECKCONTRACTVERIFY ( OP_CCV ). |
| 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 |