Date: Fri, 22 Jan 2016 23:10:42 -0500
From: "David A. Harding" <dave@dtrt.org>
To: Andrew C <achow101@gmail.com>
Message-ID: <20160123041042.GA5956@localhost.localdomain>
References: <CADToNK-O-KWZjLzKAcUz9CZB65to=bCgTfRLTVFhLVKcCjO5bA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="4Ckj6UjgE2iN1+kY"
Content-Disposition: inline
In-Reply-To: <CADToNK-O-KWZjLzKAcUz9CZB65to=bCgTfRLTVFhLVKcCjO5bA@mail.gmail.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
Cc: Bitcoin development mailing list <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] nSequence multiple uses
Precedence: list


--4Ckj6UjgE2iN1+kY
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

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.=20

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


--4Ckj6UjgE2iN1+kY
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBAgAGBQJWov1CAAoJEEspww/ynsS3MUwH/jyqghMiKBF3pwq6Ox878y74
FiLhuhtM+CMzIcTOWR/ixVaLgxxia53TonbXNdL/4ych6TA/N7l1mFJeUlHxT3QZ
hAVCNcD5CDnyX8hExvt838p3j4JNHx6nTQzT6camjM63NWO5YcPY91aLFgyXbhIX
G0IkV37H6G1b+/UYPOp9Nhkpa0zArgLUg8HeZwHs8zCsaCaQvhOLEUyp5jG7vpJC
LKVoPtjkjj5in+mMBaBFGFLEs4Juq0R/iumhwNEuF+D+9F8bciag5pjvsOOGj34b
z1tVjIE6i2jJO7GATDBUca9xEG9oP+2sW3liejYgdDH+GhUnKjwZoZmaHTfTA2M=
=5/CP
-----END PGP SIGNATURE-----

--4Ckj6UjgE2iN1+kY--