Bitcoin timelocks determine when a transaction or a specific Bitcoin output becomes eligible to be spent. They can enforce a fixed deadline based on block height or time, or require a waiting period measured from an output’s confirmation.
Understanding Bitcoin timelocks means knowing which clock controls the restriction, how the blockchain evaluates it, and why becoming eligible to spend does not guarantee immediate confirmation.
What Are Bitcoin Timelocks?
A timelock is a consensus-enforced restriction that prevents a transaction from being confirmed before a defined condition is satisfied. Bitcoin supports two principal approaches: absolute timelocks and relative timelocks.
An absolute timelock identifies a specific point that must be reached. A relative timelock establishes a minimum interval that must pass after the output being spent was confirmed. These mechanisms support arrangements such as delayed payments, recovery conditions and time-sensitive transaction protocols.
The difference is the starting reference. Absolute locks look toward a predetermined block height or time threshold, while relative locks depend on the age of the relevant output.
Absolute Timelocks: A Fixed Block Height or Time
Bitcoin transactions include an nLockTime field that can specify an absolute lock. Values below 500,000,000 represent block heights; values at or above that threshold represent Unix timestamps.
For example, a transaction using a block-height lock of 900,000 cannot become final under that condition until the blockchain reaches the required height. A timestamp-based lock instead depends on the network’s time reference.
However, timestamp-based eligibility does not rely simply on a computer’s local clock. Under Bitcoin’s consensus rules, time-based absolute locks are evaluated using Median Time Past (MTP), calculated from the timestamps of the previous 11 blocks. This helps determine when the relevant threshold has been reached.
At the script level, OP_CHECKLOCKTIMEVERIFY (CLTV) can require a spending transaction to satisfy a specified absolute locktime. The transaction must meet the script condition as well as the applicable transaction-level requirements. Also, nLockTime does not impose its intended delay if every input uses a final sequence number.
Relative Timelocks: Measuring an Output’s Age
Relative timelocks work differently because the waiting period begins in relation to the confirmation of the output being spent. Bitcoin Improvement Proposal 68 (BIP 68) defines consensus rules that interpret eligible input sequence numbers as relative lock constraints.
A block-based relative lock can require an output to age by a specified number of blocks. For instance, a 100-block constraint requires the relevant chain-height interval to pass before the spending transaction becomes eligible under that condition.
Time-based relative locks use units of 512 seconds rather than ordinary calendar timestamps. Their calculation relies on Median Time Past associated with the output’s confirmation history and subsequent blocks. Consequently, the encoded duration is a protocol-defined threshold, not a promise that a precise number of real-world minutes will pass before a transaction is confirmed.
At the script level, OP_CHECKSEQUENCEVERIFY (CSV), introduced through BIP 112, allows a spending condition to enforce a relative lock. These rules can be useful when a transaction must remain restricted for a period after an earlier transaction confirms.
When Does a Timelocked Transaction Become Valid?
A timelock threshold being reached does not automatically send Bitcoin or place a transaction in a block. The transaction must satisfy all applicable consensus and script conditions, including any remaining locks on its inputs.
Once those conditions are met, the transaction may be eligible for inclusion in a block. Actual confirmation still depends on factors such as transaction fees, network conditions and miner selection. A transaction can therefore become eligible without being confirmed immediately.
For technical reference, BIP 68 explains relative locktime rules, while Bitcoin Optech’s timelock overview outlines the relevant mechanisms.
Why Timelock Precision Matters
For digital asset systems, confusing a fixed threshold with an elapsed-age requirement can lead to incorrect assumptions about when funds become spendable. Kenson Investments examines Bitcoin mechanics and digital asset market structure to help readers assess how protocol rules influence transaction conditions and operational risk.
Sign up now for digital asset research for further analysis of Bitcoin’s underlying mechanisms.
Disclaimer: The information provided on this page is for educational and informational purposes only and should not be construed as financial advice. Crypto currency assets involve inherent risks, and past performance is not indicative of future results. Always conduct thorough research and consult with a qualified financial advisor before making investment decisions.
“The cryptocurrency and digital asset space is an emerging asset class that has not yet been regulated by the SEC and the US Federal Government. None of the information provided by Kenson LLC should be considered as financial investment advice. Please consult your Registered Financial Advisor for guidance. Kenson LLC does not offer any products regulated by the SEC, including equities, registered securities, ETFs, stocks, bonds, or equivalents.”
