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
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
|
Return-Path: <ctpacia@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 139987D
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 30 Nov 2015 03:32:42 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-qg0-f44.google.com (mail-qg0-f44.google.com
[209.85.192.44])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 95DC6145
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 30 Nov 2015 03:32:41 +0000 (UTC)
Received: by qgeb1 with SMTP id b1so110151777qge.1
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 29 Nov 2015 19:32:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
h=subject:to:references:from:message-id:date:user-agent:mime-version
:in-reply-to:content-type;
bh=tAladGMh11cYN0Vrn3/PRHZoeFInQZNcxnmKuuRJHKI=;
b=njvYvtG1+kbpOUyMGCfDhe9Ywz4luwdTLOLijRL5/cnW922OweyMGFP/fI11cGjftf
L6uEPzUDVLwTIZFl5gCH3JygPf9ok+s4Z1E8G1WJDRLk4ATpKoE8ExGq1CrTo5F6PG5y
/Fd+bXrVxu/Ont0R7rif7lvhgGk7Vo+rpxbr691YeE+HwDGmVG2SO6h9uOSJHsFXwbGo
L7ChzW9NVPslDwd+GWLhbDTL9xjPfWz0+cqrRJxbOJ3Gk0EO1nKHEQOUZyQsDVUhTiob
guFWblUrbVsm2bBQuDgOefLGmd2WxlW9qLaUuojFKXx5BQBXQDrJj9isj0HLxk/SIrCr
RoCA==
X-Received: by 10.140.43.135 with SMTP id e7mr69498645qga.11.1448854360826;
Sun, 29 Nov 2015 19:32:40 -0800 (PST)
Received: from [10.172.1.6] ([209.95.50.102]) by smtp.gmail.com with ESMTPSA id
s20sm14197533qki.31.2015.11.29.19.32.39
for <bitcoin-dev@lists.linuxfoundation.org>
(version=TLSv1/SSLv3 cipher=OTHER);
Sun, 29 Nov 2015 19:32:40 -0800 (PST)
To: bitcoin-dev@lists.linuxfoundation.org
References: <20151117004218.GB6302@savin.petertodd.org>
From: Chris <ctpacia@gmail.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <565BC352.4080001@gmail.com>
Date: Sun, 29 Nov 2015 22:32:34 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101
Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <20151117004218.GB6302@savin.petertodd.org>
Content-Type: multipart/alternative;
boundary="------------090103000300020906060408"
X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID,DKIM_VALID_AU,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: Mon, 30 Nov 2015 06:58:25 +0000
Subject: Re: [bitcoin-dev] Opt-in Full Replace-By-Fee (Full-RBF)
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: Mon, 30 Nov 2015 03:32:42 -0000
This is a multi-part message in MIME format.
--------------090103000300020906060408
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
On 11/16/2015 07:42 PM, Peter Todd via bitcoin-dev wrote:
> Sequence is used for opting in as it is the only "free-form" field
> available for that purpose. Opt-in per output was proposed as well by
> Luke-Jr, however the CTxOut data structure simply doesn't contain any
> extra fields to use for that purpose.
What is wrong with using they same scheme as sighash_single?
If input 0 has nSequence < maxint-1 then output 0 is replaceable.
For fee bumps you would just stick the change in position zero and
reduce the value.
You get FFS functionality without the hassle of addition other inputs.
--------------090103000300020906060408
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 7bit
<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
On 11/16/2015 07:42 PM, Peter Todd via bitcoin-dev wrote:<br>
<blockquote cite="mid:20151117004218.GB6302@savin.petertodd.org"
type="cite">
<pre wrap="">Sequence is used for opting in as it is the only "free-form" field
available for that purpose. Opt-in per output was proposed as well by
Luke-Jr, however the CTxOut data structure simply doesn't contain any
extra fields to use for that purpose.</pre>
</blockquote>
What is wrong with using they same scheme as sighash_single?<br>
<br>
If input 0 has nSequence < maxint-1 then output 0 is replaceable.
<br>
<br>
For fee bumps you would just stick the change in position zero and
reduce the value.<br>
<br>
You get FFS functionality without the hassle of addition other
inputs. <br>
<br>
<span style="color: rgb(34, 54, 69); font-family: 'Open Sans',
sans-serif; font-size: 34px; font-style: normal; font-variant:
normal; font-weight: normal; letter-spacing: normal; line-height:
normal; orphans: auto; text-align: start; text-indent: 0px;
text-transform: none; white-space: normal; widows: 1;
word-spacing: 0px; -webkit-text-stroke-width: 0px; display: inline
!important; float: none;"></span>
</body>
</html>
--------------090103000300020906060408--
|
