nSequence multiple uses [combined summary]

• nSequence multiple uses Andrew C 2016-01-23 04:41:55+00:00
• nSequence multiple uses David A. Harding 2016-01-23 04:10:42+00:00
• nSequence multiple uses Andrew C 2016-01-22 16:36:58+00:00

Published on: 2016-01-23T04:41:55+00:00

Summary:

During a Bitcoin-development discussion, Andrew C brought up the topic of using nSequence in Bitcoin transactions for both locktime and opt-in Replace-by-Fee (RBF) signaling. However, he realized that there is currently no way to differentiate between these two uses. In response, Dave explained that while setting nSequence to less than MAX_INT enables locktime enforcement, opting into RBF requires setting it to less than MAX-1. To provide further information, Dave shared a link to Bitcoin Improvement Proposal 125 (BIP125).Andrew then sought clarification on whether there were any plans to change nSequence to allow for distinguishing between the different features of a transaction. He suggested utilizing version bits as a potential solution.

Updated on: 2023-08-01T17:36:54.872168+00:00