In briefA consensus script rule blocking an output from being spent until a chosen block height or timestamp passes.
Also referred to as: timelocks · CLTV · CSV · nLockTime · locktime
Full explanation
Protocol rules that restrict when a Litecoin UTXO can be spent. Absolute timelocks use nLockTime or OP_CHECKLOCKTIMEVERIFY (BIP 65) against a fixed block height or Unix timestamp, while relative timelocks use OP_CHECKSEQUENCEVERIFY (BIP 112) measured from when the funding output mined.
For exampleA five-block CSV relative timelock starts counting only after the funding transaction enters a confirmed block, not when you sign.
Common mistakeAssuming a relative timelock countdown begins when you create or broadcast a transaction before it is mined into a block.
A consensus script rule blocking an output from being spent until a chosen block height or timestamp passes. Protocol rules that restrict when a Litecoin UTXO can be spent. Absolute timelocks use nLockTime or OP_CHECKLOCKTIMEVERIFY (BIP 65) against a fixed block height or Unix timestamp, while relative timelocks use OP_CHECKSEQUENCEVERIFY (BIP 112) measured from when the funding output mined.
What is a common mistake with Timelock (CLTV & CSV)?
Assuming a relative timelock countdown begins when you create or broadcast a transaction before it is mined into a block.
How is Timelock (CLTV & CSV) applied in practice?
A five-block CSV relative timelock starts counting only after the funding transaction enters a confirmed block, not when you sign. You can explore this hands-on with our Explore timelock mechanics in Transaction Lab.
Editor-in-chief of Litecoin.watch and founder of MyBank.pl. His published work covers foreign exchange, financial education and Litecoin. On Litecoin.watch, his remit includes editorial direction, source transparency and the practical guides and research published by the site.