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_PAIRCOMMIT |
|---|---|
| What the text proposes | A desk note on BIP 442 (OP_PAIRCOMMIT). The file's status is Draft. The note records the text. It does not measure who runs it. |
| Who may write | moonsettler |
| What is settled | The file's own opening line says: This BIP proposes a new tapscript opcode, `OP_PAIRCOMMIT`, which enables efficient and secure commitment to pairs of stack elements using a tagged hash construction. |
| Load-bearing assumption | Status Draft is not evidence that any node you run has shipped the change. |
| What this library says afterwards | Status on the file: Draft. A reading of the public text, not a client release note. |
| Rights | Licensed for redistribution |