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
88
89
90
91
92
93
94
95
96
97
98
99
|
Return-Path: <achow101@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 724A5D8B
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 22 Jan 2016 16:37:09 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-vk0-f48.google.com (mail-vk0-f48.google.com
[209.85.213.48])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 09B2A112
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 22 Jan 2016 16:37:08 +0000 (UTC)
Received: by mail-vk0-f48.google.com with SMTP id e185so43962975vkb.1
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 22 Jan 2016 08:37:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
h=mime-version:from:date:message-id:subject:to:content-type;
bh=W36pD7CLtKfWq6yzcKkWT9vO4ZOvBZS1Ym/IlLvDU2M=;
b=RX7K2m7koilMjaB/ygNmVxm3zqvZdL1odO8kU2OeDv1z8SI8r4DqFgu61ait3QTF9D
7ath4Sx+VOmXaM79IU7EKxoo6zHVjNLBy58Ibio3awluV/7ZeQQZmPIphuvaOC2KIf4T
J2ncQRmNfS2BLYVxLeTF0P8HpuiK8A7MgEM0zDj7LZeBj9bv3QlZt7zEBhEE8h2birJ7
w8PKNNcZ5QDUn5EOihXqRQ2jr+Xb6nxhkB1yp/+heU95mZwRJZ2yJ7/xMBqrZj1nittM
5THeqE41k6XNP0pDfXueWlw9Ps1uY4I4B0OMfMvGw/VABuncmU7yD241oIL2zfR8uB51
l0Xg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:from:date:message-id:subject:to
:content-type;
bh=W36pD7CLtKfWq6yzcKkWT9vO4ZOvBZS1Ym/IlLvDU2M=;
b=PR5nUmsQ2tPDXOB4qmWdWR90EmLqDZCa3qSZpwF5w/vq6PChS0BVBUCIddMTpP32XA
O3VPEWTH5k0sgT/SiD9nVCJ8/OmYConWYDp8kPlbHvWs/uDGXsjvEXXeISlkkSp2nuy0
HCziot2IGM2ypFUXYCUEkFivejhVhXU5SxN70SGbPbJs71U0gexXk0Z2ZrovFY3Qdh4P
aXeRu70EKcPMgEgXkt5MGeJx/JhCcemxOHqVbD3pcM0Utobk0Pw9LCxcf5sL2V2ggtPp
kA1gvp2CiBl564uno28j6tV5Iqqosdq37A1E9Nclb3R9MkdFpe/QJAqRZK5Oy64/QNkm
EX9g==
X-Gm-Message-State: AG10YOTTA5f2xmua0pW0uUT+CQIbdEBG/B0n2uHoWSsxp8ydIIQpd7T5SFQEbBpeUVcm2urAd7rKDUu/m61qJQ==
X-Received: by 10.31.52.195 with SMTP id b186mr2235389vka.39.1453480628246;
Fri, 22 Jan 2016 08:37:08 -0800 (PST)
MIME-Version: 1.0
From: Andrew C <achow101@gmail.com>
Date: Fri, 22 Jan 2016 16:36:58 +0000
Message-ID: <CADToNK-O-KWZjLzKAcUz9CZB65to=bCgTfRLTVFhLVKcCjO5bA@mail.gmail.com>
To: Bitcoin development mailing list <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary=001a1143e54288e0960529eed4d1
X-Spam-Status: No, score=-2.4 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID,DKIM_VALID_AU,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,
HTML_MESSAGE,RCVD_IN_DNSWL_LOW 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: Fri, 22 Jan 2016 16:42:28 +0000
Subject: [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: Fri, 22 Jan 2016 16:37:09 -0000
--001a1143e54288e0960529eed4d1
Content-Type: text/plain; charset=UTF-8
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
--001a1143e54288e0960529eed4d1
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">With 0.12 and opt-in RBF, nSequence will have multiple use=
s. It can be used for locktime and now signaling for opting in to RBF. Howe=
ver, there is nothing that I could find that distinguishes the uses for nSe=
quence. Spending a time locked output requires setting nSequence to less th=
an 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 R=
BF, which may not be desired behavior. Since using nSequence to signal a ce=
rtain behavior will probably be used in the future, is there any plan to ch=
ange nSequence so that the features the transaction is using can be disting=
uished? Perhaps something like version bits?=C2=A0</div><div dir=3D"ltr"><b=
r></div><div dir=3D"ltr">Thanks,</div><div dir=3D"ltr">Andrew</div>
--001a1143e54288e0960529eed4d1--
|
