Timechain
Search Donate
Sponsors
Cake Wallet, private Bitcoin and Monero walletSideShift.ai, no-signup crypto exchangeOrangeRock, non-custodial bitcoin spot and perps tradingBraiins Hashpower, buy and sell Bitcoin hashrateLayer Two Labs, drivechains for Bitcoin
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”.

Plain-English summary by Bitcoin Takeover, based on the BIP text.
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 explorer

Activated 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.

BIP 9 version bits — the first BIP 9 deployment

In Bitcoin Core

Sequence locks have been implemented as of v0.12.1, and have been buried since v0.19.0.

0:000:00