Author: Jeremy 2021-09-05 03:19:57
Published on: 2021-09-05T03:19:57+00:00
In a recent discussion among Bitcoin developers, the issue of sequence values used by wallet implementations was brought up. Specifically, the question was whether any other numbers besides 0xfffffffd (the sequence number that is rbf-opt-in and csv-opt-out) are currently expected by any wallet software to be broadcastable with the DISABLE flag set. The Bitcoin Core script test uses this number, but it's unclear if others do as well. The discussion also touched on the advantages of using 0xfffffffd versus just 0, and whether people commonly use 0xfffffffd. While 0xfffffffe is considered special, it seems that the former has the alternative of either a 0-valued sequence lock or a 1. This conversation was prompted by a flaw in the Sequence lock implementation regarding upgradability, which Jeremy Rubin noticed recently. He proposed a patch for the issue on GitHub, but suggested widely surveying the community before making any changes to ensure that no one is depending on the current semantics in any live application. Rubin also published a blog post explaining the defect and his proposed solution.
Updated on: 2023-06-15T01:28:51.239635+00:00