1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
|
Return-Path: <dave@dtrt.org>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id DBBF4104D
for <bitcoin-dev@lists.linuxfoundation.org>;
Sat, 23 Jan 2016 04:11:33 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from mail.dtrt.org (mail.dtrt.org [207.192.75.234])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 72476126
for <bitcoin-dev@lists.linuxfoundation.org>;
Sat, 23 Jan 2016 04:11:33 +0000 (UTC)
Received: from harding by mail.dtrt.org with local (Exim 4.72)
(envelope-from <dave@dtrt.org>)
id 1aMpXw-00062Z-2P; Fri, 22 Jan 2016 23:11:32 -0500
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)
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RP_MATCHES_RCVD
autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
X-Mailman-Approved-At: Sat, 23 Jan 2016 04:27:31 +0000
Cc: Bitcoin development mailing list <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] nSequence multiple uses
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Development Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Sat, 23 Jan 2016 04:11:34 -0000
--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--
|
