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

A lock measured from confirmation.

Sequence fields can express relative transaction locks based on the age of the outputs being spent.

Read the explanation
← All standards

Why it exists

BIP 68 gives certain transaction input sequence numbers a relative-locktime meaning. Instead of asking for a fixed date or height, a transaction can require its input coins to age after confirmation. The delay is tied to each spent output, which is useful when the funding date is not known in advance.

How it works

The rules apply to transaction versions of at least 2 when the sequence disable flag is clear. A type flag chooses block counts or units of 512 seconds; the low 16 bits encode the delay. Time-based evaluation uses median-time-past rules rather than a device’s wall clock.

Every enabled input lock must be satisfied before the transaction can be included. BIP 68 constrains the transaction that contains those sequence values. To require a spender to select a suitable relative lock rather than omit it, a funding script uses CHECKSEQUENCEVERIFY from BIP 112.

PUT IT IN CONTEXT

A practical example

If an input’s output confirms at height 900,000 and its spending transaction specifies a relative delay of 144 blocks, that input permits inclusion at height 900,144 or later. A second input with a later maturity can delay the whole transaction further. Creating or signing the transaction in advance does not start the clock; confirmation of the funding output does.

What to keep in mind

A block-based 144-block delay is roughly a day on average, not a guaranteed 24 hours. Reorganizations can change confirmation history and eligibility. A transaction-level relative lock is also not an inheritance policy by itself: the keys and script constraints still determine who can spend.

Status & implementation

Bitcoin Core implemented sequence locks in 0.12.1 and documents the activation as buried since 0.19.0. These are consensus rules rather than optional wallet preferences.

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