Protocol specification booklets and an engineering notebook, editorial illustration
BIP 65 / CONSENSUS

A lock until a point in time.

CHECKLOCKTIMEVERIFY can require a spending transaction to respect an absolute block-height or time lock.

Read the explanation
← All standards

Why it exists

BIP 65 adds CHECKLOCKTIMEVERIFY, usually shortened to CLTV. It lets a spending script require an absolute block height or time condition. Putting the condition inside the funded script prevents a key holder from avoiding the delay simply by signing a different transaction without a locktime.

How it works

CLTV checks the spending transaction’s nLockTime against the script’s required value. The types must agree: a height cannot be substituted for a timestamp. The spending input must also use a non-final sequence value so transaction locktime remains effective. Ordinary transaction finality rules then determine when inclusion is permitted.

The opcode does not supply a signature or transfer the coins automatically. It only checks one condition, and the rest of the script must still succeed. A script may offer another branch with different requirements, so a delayed branch does not necessarily mean every possible spend is delayed.

PUT IT IN CONTEXT

A practical example

Imagine a recovery branch requiring a designated key and a height lock of 1,000,000. The recovery transaction must use a matching height-based nLockTime at least that large and satisfy the key check. With nLockTime exactly 1,000,000, ordinary finality makes block 1,000,001 the first eligible height. A separate cooperative branch could allow spending earlier if its own requirements are met.

What to keep in mind

Block height is not an exact calendar date. Timestamp locks use Bitcoin’s applicable time rules, not the clock on a phone. Recovery software must preserve the script and construct a compatible transaction; reaching the deadline alone does not recover anything.

Status & implementation

CLTV is an activated consensus feature. Bitcoin Core merged it in 0.12.0 and backported support to earlier releases; its activation is recorded as a buried height rule.

Specification status: Deployed · Sources checked 13 November 2026

Read the sources

Put the standard in context.

Explore the practical guide

Find your next answer.

Search the complete field guide · Esc to close