BIP68: Relative lock-time through consensus-enforced sequence numbers (update)



Summary:

For the past five months, work on creating a relative lock-time proposal using sequence numbers has been ongoing. The implementation can be found at https://github.com/bitcoin/bitcoin/pull/6312. The current implementation is mempool-only, and the soft-fork would be deployed at a later stage. There has been various discussion back and forth to refine the details over these months. The BIP text has been updated according to the details that were discussed in mid-October and has extensively clarified the text. To recap, the overall picture for relative lock-time is that BIP68 introduces consensus rules using some of the nSequence field, while BIP112 creates a new opcode OP_CHECKSEQUENCEVERIFY (PR #6564) so relative lock-time can be verified from the Bitcoin scripting language. Ideally, it would be best to soft-fork BIP68, BIP112 (CSV), and 113 (MTP) together. BIP113 has already been deployed in 0.11.2 as mempool policy so miners should be applying this policy as they deploy version 4 blocks for the ongoing CLTV soft-fork (currently at 42% at the time of writing).


Updated on: 2023-06-11T01:19:05.074500+00:00