Bitcoin Takeover / BIPs / BIP 112
BIP 112
CHECKSEQUENCEVERIFY
Deployed Activated soft fork Consensus (soft fork) Specification Assigned 2015-08-10
OP_CHECKSEQUENCEVERIFY: scripts can enforce relative timelocks. A core ingredient of Lightning.
From the BIP’s abstract
This BIP describes a new opcode (CHECKSEQUENCEVERIFY) for the Bitcoin scripting system that in combination with BIP 68 allows execution pathways of a script to be restricted based on the age of the output being spent.
Read BIP 112 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
The CHECKSEQUENCEVERIFY opcode has been implemented since v0.12.1, and has been buried since v0.19.0.
Authors
In the Bitcoin Takeover Wiki
- Eric Lombrozo People