📅 Original date posted:2016-01-22
📝 Original message:With 0.12 and opt-in RBF, nSequence will have multiple uses. It can be used
for locktime and now signaling for opting in to RBF. However, there is
nothing that I could find that distinguishes the uses for nSequence.
Spending a time locked output requires setting nSequence to less than
MAX_INT but opting into RBF also requires setting nSequence to less than
MAX_INT. By spending a time locked output, you would also be opting into
RBF, which may not be desired behavior. Since using nSequence to signal a
certain behavior will probably be used in the future, is there any plan to
change nSequence so that the features the transaction is using can be
distinguished? Perhaps something like version bits?
Thanks,
Andrew
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20160122/790e817d/attachment.html>;
Andrew C [ARCHIVE] /
npub1vc…xz0wk
2023-06-07 17:48:05
in reply to nevent1q…tuhm
Author Public Key
npub1vceyhqxfhemlfq82ztdv9gqgc08zq2680yzy4dfuly7h8pqrkwps0xz0wkPublished at
2023-06-07 17:48:05Event JSON
{
"id": "3a9fdb1e71bb8724338888540ae9bc6e660c17e1c2f8cf3cddbc75a4eff67471",
"pubkey": "66324b80c9be77f480ea12dac2a008c3ce202b4779044ab53cf93d738403b383",
"created_at": 1686160085,
"kind": 1,
"tags": [
[
"e",
"a892d172b2cf68cca89371cb878b2cb2ae6924ec73f730aae073a374be6865b4",
"",
"reply"
],
[
"p",
"a23dbf6c6cc83e14cc3df4e56cc71845f611908084cfe620e83e40c06ccdd3d0"
]
],
"content": "📅 Original date posted:2016-01-22\n📝 Original message:With 0.12 and opt-in RBF, nSequence will have multiple uses. It can be used\nfor locktime and now signaling for opting in to RBF. However, there is\nnothing that I could find that distinguishes the uses for nSequence.\nSpending a time locked output requires setting nSequence to less than\nMAX_INT but opting into RBF also requires setting nSequence to less than\nMAX_INT. By spending a time locked output, you would also be opting into\nRBF, which may not be desired behavior. Since using nSequence to signal a\ncertain behavior will probably be used in the future, is there any plan to\nchange nSequence so that the features the transaction is using can be\ndistinguished? Perhaps something like version bits?\n\nThanks,\nAndrew\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20160122/790e817d/attachment.html\u003e",
"sig": "dae4dd7d4bebbd088837748fb2790c87acb3a20526242572310630ce711cc854bec60efa0c34bcce4de7653e16cf18503ffa975a63428c15923e1f251bf6940e"
}