What will replace OP_CHECKLOCKTIMEVERIFY & OP_CHECKSEQUENCEVERIFY after the Genesis upgrade?

Since these two opcodes will be removed after Genesis and (from my understanding) nLockTime works in a slightly different way (prevents transaction from being included in a block vs. UTXO being locked until given time/block height), how will be possible to achieve same functionality after that?

Is it possible to build a locking/redeem script using other opcodes that achieves the same result? Or is there something else?

Submit an answer See answers Share on Twitter Share on Facebook
Accepted Answer

Accepted: Use nLockTime with an offline transaction

These two opcodes are unnecessary as the same functionality can be achieved via using nLockTime in an offline transaction.

If wanting to create a transaction that is valid on 1/1/2021, simply create an offline transaction with nLockTime equal to then and do not broadcast it to the network. This transaction can be stored in a trust, deposit box, or the raw TX encrypted on-chain.

Additionally, multi-signature requirements can be added for trust among multiple parties.

See the following blog posts for further references and explanations on how it can be done w/out the custom opcodes:



Satoshi’s explanation on why CLTV is unnecessary and how we can achieve the same with nLockTime:


You are creating this answer as an anonymous user. If you log in we will be able to store the draft as you write it.

Submit an Answer

By swiping I acknowledge that the answer will be immutably stored on the Bitcoin SV blockchain forever and that I take full responsibility for any legal or other consequences that might be related to that.
Made with in Slovenia.