Bitcoin Takeover / BIPs / BIP 68
BIP 68
Relative lock-time using consensus-enforced sequence numbers
Deployed Activated soft fork Consensus (soft fork) Specification Assigned 2015-05-28
Relative lock-time via the nSequence field: “not before N blocks after the coin confirmed”.
From the BIP’s abstract
This BIP introduces relative lock-time (RLT) consensus-enforced semantics of the sequence number field to enable a signed transaction input to remain invalid for a defined period of time after confirmation of its corresponding outpoint.
Read BIP 68 on GitHubFind in explorerActivated on mainnet
CSV · Relative timelocks — block 419,328, 2016-07-04.
“Spendable N blocks after this coin confirmed” (relative timelocks) plus median-time-past for lock times. Lightning's penalty and timeout paths rely on it.
Sources: BIP 68, “Relative lock-time using consensus-enforced sequence numbers”, bitcoin/bips (commit a7f9132, 2026-11-17) · BIP 112, “CHECKSEQUENCEVERIFY”, bitcoin/bips (commit a7f9132, 2026-11-17) · BIP 113, “Median time-past as endpoint for lock-time calculations”, bitcoin/bips (commit a7f9132, 2026-11-17) · Bitcoin Core, src/kernel/chainparams.cpp — mainnet BIP34/65/66/CSV/SegWit heights · mempool.space, block 419,328
In Bitcoin Core
Sequence locks have been implemented as of v0.12.1, and have been buried since v0.19.0.