Why it exists
BIP 112 adds CHECKSEQUENCEVERIFY, or CSV, so a Bitcoin script can demand a relative delay. It connects the age-based transaction rules of BIP 68 to a particular spending branch. That makes a delay enforceable even when the person holding a spending key would prefer to remove it.
How it works
CSV compares the script’s requirement with the relevant input’s sequence field. For an enabled delay, the transaction version, disable flag, lock type and encoded value must all be suitable. BIP 68 then checks whether the output has actually aged enough for the transaction to be included.
The timer is tied to confirmation of the output being spent. A script can contain an immediate cooperative or revocation path and a delayed unilateral path. This is useful in payment-channel constructions because the response window starts when a commitment reaches the chain, rather than expiring on a fixed calendar date.
A practical example
A channel commitment could allow its broadcaster to claim one output only after 144 blocks, while a valid revocation branch lets the other party act sooner. If an obsolete commitment confirms, the counterparty’s monitoring software has the delay window to react. The script does not notify anyone: the surrounding channel software must recognize the event and prepare the appropriate response.
What to keep in mind
CSV is a condition, not a complete channel protocol. Correct keys, revocation handling, fee planning and monitoring remain necessary. Block delays are not exact durations, and spending through another valid branch may bypass the delayed branch entirely by design.
Status & implementation
Bitcoin Core implemented CSV in 0.12.1 and records its activation as buried since 0.19.0. BIP 112’s examples explain channel applications; they are not a complete modern Lightning implementation.
Specification status: Deployed · Sources checked 13 November 2026
