Bitcoin Covenants: What OP_CHECKTEMPLATEVERIFY Would Add

OP_CHECKTEMPLATEVERIFY, commonly shortened to CTV, is a proposed Bitcoin covenant design that would let a Bitcoin output define what the next spending transaction must look like. In practical terms, the output can commit to a specific transaction template before it is spent.

That matters because it expands what Bitcoin scripts can coordinate without requiring users or services to manage sets of pre-signed transactions. According to the source material, CTV could support trust-minimized vaults, congestion control, and smart contract primitives while keeping the spending path constrained by the committed transaction structure.

Vaults are one of the clearest use cases described. By predefining how funds can move next, CTV-style covenants could help create recovery or delay mechanisms that reduce reliance on trusted operators or fragile key-handling arrangements.

The proposal is also relevant to network congestion. If future transactions can be committed to in a structured way, users and services may be able to coordinate batched or staged spending patterns more efficiently, depending on how such systems are implemented.

CTV is part of the broader discussion around Bitcoin covenants, a category of scripting ideas focused on restricting how coins may be spent in future transactions. The central tradeoff is how to add more expressive transaction controls while preserving Bitcoin’s conservative design assumptions.