OP_CHECKTEMPLATEVERIFY (CTV)

Definition: OP_CHECKTEMPLATEVERIFY (CTV) is a proposed Bitcoin Script opcode described in BIP 119. It would require a transaction spending an output to match a committed template for selected transaction fields. CTV remains a Draft proposal and is not active in Bitcoin consensus, so it cannot currently enforce a covenant on Bitcoin mainnet.1

Official proposalBitcoin Improvement Proposal 119 (BIP 119)
DirectoriesBitcoin Directory

How the template commitment works

BIP 119 proposes changing the meaning of the currently reserved OP_NOP4 opcode through a Bitcoin soft fork. Under the proposal, a script supplies a 32-byte hash. When the opcode runs, the node calculates a hash from defined parts of the transaction that is trying to spend the output and compares it with that value. The committed data includes fields such as the transaction version and locktime, input count and sequences, output count and outputs, and the index of the input being spent. If the calculated value does not match the committed hash, validation fails under the proposed rules.1

This creates a limited covenant: an output can constrain how a later transaction spends it by committing to a transaction template. The commitment does not describe every possible condition a general-purpose smart-contract language might express. Instead, it offers a narrow way to make a spending transaction follow specified structural details. Wallets and applications would still need to construct the script and transaction correctly, communicate the expected spend, and account for fees and recovery procedures.12

Potential uses proposed for CTV

CTV proponents have described several possible applications. These are design proposals that depend on a consensus change; they are not services or mainnet features users can turn on today.

ApplicationHow a template commitment could helpImportant condition
Congestion controlA transaction could commit to a follow-up transaction that distributes funds to multiple recipients later.Recipients may need to wait for the follow-up transaction, and its fees still need to be funded.
Channel factories and joinpoolsParticipants could commit to preset exit or state-transition transactions, reducing some rounds of signing or the need to exchange many presigned transactions.Participants must still understand the committed transaction paths and recovery options.
Vault designsA preset template could constrain a withdrawal path or route funds through a recovery step.CTV alone does not supply a complete vault product; wallet software and a complete policy are still needed.
Discreet Log ContractsTemplate hashes could reduce how much outcome-specific data participants need to exchange and store in some constructions.The contract design, oracle data, and any remaining signatures or adaptors still matter.

Bitcoin Optech describes these as possible constructions and also notes that CTV can be combined with or compared against other proposed upgrades. The practical value of a design depends on the details: what transaction fields are fixed, whether participants can exit safely, how fees will be paid, and which wallets or services support the workflow.2

Limits, alternatives, and debate

CTV is intentionally narrower than a general covenant system. Its supporters argue that a limited template commitment can enable useful spending patterns while keeping the opcode and its validation rules relatively simple. Critics have questioned whether the proposed feature is flexible enough, whether some uses would be better handled by a more composable design, and whether a consensus change is justified before applications and public experimentation demonstrate enough value. The proposal also has to account for fee uncertainty: a template may be created before its future transaction is broadcast, so users may need a way to add fees without invalidating the intended transaction.23

Alternatives discussed in Bitcoin development include presigned transactions and other proposed script or signature changes, such as SIGHASH_ANYPREVOUT and combinations involving OP_CAT and OP_CHECKSIGFROMSTACK. These approaches have different tradeoffs in flexibility, transaction size, coordination, and implementation complexity. None should be treated as interchangeable without analyzing the particular contract or wallet design.2

CTV is not active on mainnet

The BIP 119 document lists the proposal as Draft. It specifies that before activation, nodes must treat OP_NOP4 as a no-op for consensus validation, even though local policy may discourage transactions using it in certain contexts. In other words, a script that assumes CTV rules are already enforced cannot rely on Bitcoin mainnet to enforce those rules. Do not treat a CTV-based output as a live covenant unless the network has activated compatible consensus rules and the wallet software explicitly supports the resulting design.1

History

  • January 6, 2020: BIP 119 was assigned to the CHECKTEMPLATEVERIFY proposal. The BIP describes a proposed soft fork that would give OP_NOP4 the CTV behavior.1
  • April 2022: A proposed miner-signaling and activation plan prompted discussion about CTV’s benefits, risks, and alternatives. The plan was not itself activation; the proposal remains Draft in the BIP repository.3

Page updated: November 10, 2026.

Related Terms

Related Articles

See Also

Sources

  1. Bitcoin Improvement Proposals. “BIP 119: CHECKTEMPLATEVERIFY.” Assigned January 6, 2020. Status: Draft. Accessed November 10, 2026. BIP 119.
  2. Bitcoin Optech. “OP_CHECKTEMPLATEVERIFY.” Accessed November 10, 2026. CTV topic guide.
  3. Bitcoin Optech. “Newsletter #197.” April 27, 2022. Discussion about activating CTV.