BOLT 3 use of unallocated/reserved nLockTime & nSequence space



Summary:

Mark Friedenbach, a protocol engineer, discovered that BOLT 3 uses a technique to encode the commitment transaction number split across the transaction’s nLockTime and input’s nSequence number. This method utilizes 7.34% of the currently unallocated but usable space in nLockTime and 0.78% of unallocated but usable space in nSequence. However, Mark points out that this use of reserved space may not always be available for future protocol upgrades. He suggests those involved in crafting the BOLT 3 specification propose allocating this space for data storage to protect it from future changes while informing the wider developer community of reserved space usage.


Updated on: 2023-05-24T02:37:08.424917+00:00