MIME-Version: 1.0
References: <CADToNK-O-KWZjLzKAcUz9CZB65to=bCgTfRLTVFhLVKcCjO5bA@mail.gmail.com>
	<20160123041042.GA5956@localhost.localdomain>
In-Reply-To: <20160123041042.GA5956@localhost.localdomain>
From: Andrew C <achow101@gmail.com>
Date: Sat, 23 Jan 2016 04:41:55 +0000
Message-ID: <CADToNK96HTcz+pjdQgo7XO2wNhaTkCsAHWbO=WZNPKM0_L4MwQ@mail.gmail.com>
To: "David A. Harding" <dave@dtrt.org>
Content-Type: multipart/alternative; boundary=001a1143e54229f60a0529f8f530
Cc: Bitcoin development mailing list <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] nSequence multiple uses
Precedence: list

--001a1143e54229f60a0529f8f530
Content-Type: text/plain; charset=UTF-8

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@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
>
>

--001a1143e54229f60a0529f8f530
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Ahh. I see. Thanks, I must have missed that when going thr=
ough the BIP. Guess I need to read more carefully next time.<div><br></div>=
<div>Thanks,</div><div>Andrew</div></div><br><div class=3D"gmail_quote"><di=
v dir=3D"ltr">On Fri, Jan 22, 2016 at 11:11 PM David A. Harding &lt;<a href=
=3D"mailto:dave@dtrt.org">dave@dtrt.org</a>&gt; wrote:<br></div><blockquote=
 class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc soli=
d;padding-left:1ex">On Fri, Jan 22, 2016 at 04:36:58PM +0000, Andrew C via =
bitcoin-dev wrote:<br>
&gt; Spending a time locked output requires setting nSequence to less than<=
br>
&gt; MAX_INT but opting into RBF also requires setting nSequence to less th=
an<br>
&gt; MAX_INT.<br>
<br>
Hi Andrew,<br>
<br>
Opt-in RBF requires setting nSequence to less than MAX-1 (not merely<br>
less than MAX), so an nSequence of exactly MAX-1 (which appears in<br>
hex-encoded serialized transactions as feffffff) enables locktime<br>
enforcement but doesn&#39;t opt in to RBF.<br>
<br>
For more information, please see BIP125:<br>
<br>
=C2=A0 =C2=A0 <a href=3D"https://github.com/bitcoin/bips/blob/master/bip-01=
25.mediawiki" rel=3D"noreferrer" target=3D"_blank">https://github.com/bitco=
in/bips/blob/master/bip-0125.mediawiki</a><br>
<br>
-Dave<br>
<br>
</blockquote></div>

--001a1143e54229f60a0529f8f530--