Author: Mark Friedenbach 2015-07-05 17:07:12
Published on: 2015-07-05T17:07:12+00:00
A proposal has been made to shift the semantics of nSequence in BIP 68 to specify 0 relative locktime instead of 1, as it currently does. This change would allow transactions to have an effective nLocktime without requiring at least one input to be mined ahead of its parent. The proposal suggests using MAX_INT - 1 to specify 0 relative locktime. It is noted that this change would preserve the semantics of transactions that have already been created with the specific nSequence value of MAX_INT - 1. Bitcoin Core may switch to implementing this change for cases where the sequence number field is set to 0.
Updated on: 2023-06-10T02:09:33.383507+00:00