OP_CHECKTEMPLATEVERIFY is the BIP119 covenant proposal that would require a spending transaction to match a hash commitment to selected transaction-template fields.
CTV commits to structure without providing a general introspection language. [BIP 119 — CHECKTEMPLATEVERIFY] [Bitcoin Optech — OP_CHECKTEMPLATEVERIFY]
Proposed uses include vault paths, payment pools and congestion control. [BIP 119 — CHECKTEMPLATEVERIFY] [CTV reference]
Publication as a BIP does not mean the opcode is active; activation would require Bitcoin consensus change. [Bitcoin Optech — OP_CHECKTEMPLATEVERIFY] [CTV reference]
CTV commits to structure without providing a general introspection language. [CTV reference] [Bitcoin Core — Script interpreter]
Proposed uses include vault paths, payment pools and congestion control. [BIP 119 — CHECKTEMPLATEVERIFY] [Bitcoin Developer Reference — Contracts and scripts]
Publication as a BIP does not mean the opcode is active; activation would require Bitcoin consensus change. [Bitcoin Core — Script interpreter] [Bitcoin Developer Reference — Contracts and scripts]
CTV commits to structure without providing a general introspection language. [CTV reference] [Delving Bitcoin — CTV discussions]
Proposed uses include vault paths, payment pools and congestion control. [Bitcoin Optech — OP_CHECKTEMPLATEVERIFY] [Bitcoin Core — Script interpreter]
Publication as a BIP does not mean the opcode is active; activation would require Bitcoin consensus change. [BIP 119 — CHECKTEMPLATEVERIFY] [Delving Bitcoin — CTV discussions]
CTV commits to structure without providing a general introspection language. [Bitcoin Developer Reference — Contracts and scripts] [Delving Bitcoin — CTV discussions]
For the clearest picture, read this entry together with Bitcoin covenants, Timelock, Consensus rules, Bitcoin Script. The reverse links also lead from Bitcoin covenants, Bitcoin Vault.