š
Original date posted:2016-01-23
š Original message:Ahh. I see. Thanks, I must have missed that when going through the BIP.
Guess I need to read more carefully next time.
Thanks,
Andrew
On Fri, Jan 22, 2016 at 11:11 PM David A. Harding <dave at dtrt.org> wrote:
> On Fri, Jan 22, 2016 at 04:36:58PM +0000, Andrew C via bitcoin-dev wrote:
> > 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.
>
> Hi Andrew,
>
> Opt-in RBF requires setting nSequence to less than MAX-1 (not merely
> less than MAX), so an nSequence of exactly MAX-1 (which appears in
> hex-encoded serialized transactions as feffffff) enables locktime
> enforcement but doesn't opt in to RBF.
>
> For more information, please see BIP125:
>
> https://github.com/bitcoin/bips/blob/master/bip-0125.mediawiki
>
> -Dave
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20160123/1fa99b48/attachment.html>;
Andrew C [ARCHIVE] /
npub1vcā¦xz0wk
2023-06-07 17:48:05
in reply to nevent1qā¦255p
Author Public Key
npub1vceyhqxfhemlfq82ztdv9gqgc08zq2680yzy4dfuly7h8pqrkwps0xz0wkSeen on
wss://relay.nostr.bandPublished at
2023-06-07 17:48:05Event JSON
{
"id": "15d6b1b6ea79cf08f341d522d2ad996e29d8aa1b76ad99f7b862b863ae70988a",
"pubkey": "66324b80c9be77f480ea12dac2a008c3ce202b4779044ab53cf93d738403b383",
"created_at": 1686160085,
"kind": 1,
"tags": [
[
"e",
"a892d172b2cf68cca89371cb878b2cb2ae6924ec73f730aae073a374be6865b4",
"",
"root"
],
[
"e",
"68c96c37edea82a21057f352d59503a3c3180c54da60be5bec71f7fc5da54793",
"",
"reply"
],
[
"p",
"d3574a24208f4e3d0821bb4a69a0c3ae842043d444fa5c4a8c49c369918a6fb2"
]
],
"content": "š
Original date posted:2016-01-23\nš Original message:Ahh. I see. Thanks, I must have missed that when going through the BIP.\nGuess I need to read more carefully next time.\n\nThanks,\nAndrew\n\nOn Fri, Jan 22, 2016 at 11:11 PM David A. Harding \u003cdave at dtrt.org\u003e wrote:\n\n\u003e On Fri, Jan 22, 2016 at 04:36:58PM +0000, Andrew C via bitcoin-dev wrote:\n\u003e \u003e Spending a time locked output requires setting nSequence to less than\n\u003e \u003e MAX_INT but opting into RBF also requires setting nSequence to less than\n\u003e \u003e MAX_INT.\n\u003e\n\u003e Hi Andrew,\n\u003e\n\u003e Opt-in RBF requires setting nSequence to less than MAX-1 (not merely\n\u003e less than MAX), so an nSequence of exactly MAX-1 (which appears in\n\u003e hex-encoded serialized transactions as feffffff) enables locktime\n\u003e enforcement but doesn't opt in to RBF.\n\u003e\n\u003e For more information, please see BIP125:\n\u003e\n\u003e https://github.com/bitcoin/bips/blob/master/bip-0125.mediawiki\n\u003e\n\u003e -Dave\n\u003e\n\u003e\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20160123/1fa99b48/attachment.html\u003e",
"sig": "0115851f36403fedf0dbbb1072fddfbe919f490fe6863de765384490397602237227ac6529c84ea9eef55653cc6213843779b2214bc6ae5ae2b453974828d94e"
}