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_CHECKLOCKTIMEVERIFY |
|---|---|
| What the text proposes | BIP 65, OP_CHECKLOCKTIMEVERIFY. A new opcode (OP_CHECKLOCKTIMEVERIFY) for the Bitcoin scripting system that allows a transaction output to be made unspendable until some point in the future. |
| Who may write | Peter Todd |
| What is settled | A new opcode (OP_CHECKLOCKTIMEVERIFY) for the Bitcoin scripting system that allows a transaction output to be made unspendable until some point in the future. |
| 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: Deployed. A reading of the public specification, not a copy of it and not a certification. |
| Rights | Official external source only |