summaryrefslogtreecommitdiff
path: root/c5/08f5687f224986fb701895def9fae816f0016f
blob: 952e36c6ba933704f989a02ea3b5fc6f902aa4df (plain)
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
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
Return-Path: <maxim.solovjov@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id 255B0D28
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Wed, 11 Apr 2018 19:58:49 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-wm0-f44.google.com (mail-wm0-f44.google.com [74.125.82.44])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 1A5A5628
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Wed, 11 Apr 2018 19:58:48 +0000 (UTC)
Received: by mail-wm0-f44.google.com with SMTP id l16so2098493wmh.2
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Wed, 11 Apr 2018 12:58:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
	h=mime-version:in-reply-to:references:from:date:message-id:subject:to
	:cc; bh=0dqCu9PYcd98YXYYWjl4jyzcb8BcCabLkoxDuGSrXqA=;
	b=DgLLEBnYBxycAW5k2W74rPcS/39hm/SffA9USn4yRpRfI6Tw0kUKIz5Zedlu6x+yqT
	tG7hHUrxhcmu7ytZ6X3UiCKNiaqgwZ1fHIGgEsZ3h+wxDVx/PLf/pOg/PWcEbNSFXU1M
	QRDwguJa/WtMkIRrZV3ESe44xEhUxifzwBMTnnfEmll18HbaFpQB+rEWw/1HMD3Egxku
	XAA1hGIL/uPusuvJZHdA6vzOYvQShVU4K5M3e8JUuhvIszJ2rCQWhoUWxq4jm0PdGA6a
	AmswuYK7h1zFqJZ0ClpLTccrVjD7M0jLqRWHpqUrdDbf/tUeBUJcbp9BCJK5vK2Cuym7
	ObCw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:mime-version:in-reply-to:references:from:date
	:message-id:subject:to:cc;
	bh=0dqCu9PYcd98YXYYWjl4jyzcb8BcCabLkoxDuGSrXqA=;
	b=Y55ihkX3d3GakrF4//S8wz+qu7Ywpf8sVLcL5TYvaC637CFFY7HLchvgvtdQG9DJp1
	ztVNTKDmGjcMFmOJ7JT/axF0tmWJ2ssHzmTVOU7JMXSMMbe4wUJy2VuXoMqXE7py/rxf
	LVnr7sQac41fmrE0Tq84/tUHf4+CVNuaVPle3EpgIEpN0s0EfCP3AtsyydicMBa8303f
	8yqFu8WzTG/cnNxuovcCG/KEaD6XqsSARq2K4ajVt4Hf7yjY1T/AtDctRbhpiHRiYCbd
	VMhdbpNUuJdJROeTHQ0VINs+Wn2r9hQofXEzFrMqHT1Q94BQKS1ZOJ5KzYWxXtPi0Hzg
	6wyw==
X-Gm-Message-State: ALQs6tC0ngPQLnOf2ZqAjA8dtiKbjoz/FgTeXnDP1ttpEUpVN3Rar6Wd
	biHRG4RQ3YxdZYCySZcGctYgyWtefcwHUoz5MZ0=
X-Google-Smtp-Source: AIpwx4/hE6LbVpRZblweZjnH9DyZq9J8TjpXfJdalqnQnVIQzkEWzRGdITpddL3qY2ArJX7AjPiITcRouq6Fgl+nbbs=
X-Received: by 10.28.27.194 with SMTP id b185mr3847966wmb.57.1523476726525;
	Wed, 11 Apr 2018 12:58:46 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.152.83 with HTTP; Wed, 11 Apr 2018 12:58:45 -0700 (PDT)
In-Reply-To: <CALJw2w6T6+ZTtsWGoqicuL6r3A0X_Ru379aH_7JcxnBaUiFfkQ@mail.gmail.com>
References: <CAO11aqjomkZcr8yeKtT5M8VUROGwz56w11UzR0pDBu333=BEPg@mail.gmail.com>
	<CALJw2w6Guc6rX7A_8Nqob+w1=NKi2DfH9aj2-sg2EfgRFjDw0g@mail.gmail.com>
	<CALJw2w5wfVt160uywmfOjhON8EbYkjg9bCU-6EKBO2y9TYFY5A@mail.gmail.com>
	<20180411075225.GG20665@savin.petertodd.org>
	<CALJw2w6OJZLrf20R--EYECPE65H0EJPxyUHRbSOJGQc9SNvupA@mail.gmail.com>
	<20180411093724.GA21441@savin.petertodd.org>
	<W-3_0a0Wp9HoQBvu-eGzXlwpj63Kk4kAGWECRax6CqdvML961niOTYkq60sv381rS-ffpQGG-apaTtvHkjkobNVlyXAG_WSekXevGmaOS5Q=@protonmail.com>
	<CALJw2w6T6+ZTtsWGoqicuL6r3A0X_Ru379aH_7JcxnBaUiFfkQ@mail.gmail.com>
From: Maksim Solovjov <maxim.solovjov@gmail.com>
Date: Wed, 11 Apr 2018 22:58:45 +0300
Message-ID: <CAO11aqiipgo8tty2qiA0Jr1SiDjE51VbeUJBR4O9_Nyzm5EXBg@mail.gmail.com>
To: Karl-Johan Alm <karljohan-alm@garage.co.jp>, 
	Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary="001a114b3aae1bb3f80569981169"
X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, HTML_MESSAGE,
	RCVD_IN_DNSWL_NONE 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: Wed, 11 Apr 2018 20:17:31 +0000
Subject: Re: [bitcoin-dev] Few questions regarding ListTransaction
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Protocol 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: Wed, 11 Apr 2018 19:58:49 -0000

--001a114b3aae1bb3f80569981169
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

OK.

Thank you guys for clarification.

On Wed, Apr 11, 2018 at 1:00 PM, Karl-Johan Alm via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:

> Thanks for clarifying!
>
> On Wed, Apr 11, 2018 at 6:48 PM, ZmnSCPxj <ZmnSCPxj@protonmail.com> wrote=
:
> > Good morning Karl-Johan Alm,
> >
> > To clarify:
> >
> > Nothing prevents a miner from completely ignoring nSequence when puttin=
g
> transactions in blocks.
> >
> > Unconfirmed transactions are, by definition, not recorded in blocks.  S=
o
> if there is a transaction 0xFFFFFFF nSequence and fee 1000 satoshi, and
> another conflicting transaction 0xFFFFFFF nSequence and fee 100000000
> satoshi, miners can include the latter one even if the first one came to
> their knowledge first, regardless nSequence.
> >
> > Thus, in the end "full replace-by-fee", where nSequence is IGNORED for
> purposes of replace-by-fee, is expected to become the norm, and we should
> really be designing our wallets and so on so that we only trust
> transactions that have confirmations.
> >
> > The "nSequence=3D0xFFFFFFFF means opt-OUT of RBF" convention is only
> followed by fullnodes running standard bitcoind.  Nothing prevents miners
> from running patched bitcoind that ignores this rule, and connecting with
> similar peers who also ignore this rule.
> >
> > Regards,
> > ZmnSCPxj
> >
> >
> > Sent with ProtonMail Secure Email.
> >
> > =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 Origina=
l Message =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90
> >
> > On April 11, 2018 5:37 PM, Peter Todd via bitcoin-dev <
> bitcoin-dev@lists.linuxfoundation.org> wrote:
> >
> >> On Wed, Apr 11, 2018 at 05:10:43PM +0900, Karl-Johan Alm wrote:
> >>
> >> > On Wed, Apr 11, 2018 at 4:52 PM, Peter Todd pete@petertodd.org wrote=
:
> >> >
> >> > > Or via full replace-by-fee, which appears to be used by a
> significant minority
> >> > >
> >> > > of miners:
> >> >
> >> > I was of the impression that final transactions (sequence=3D0xffffff=
ff)
> >> >
> >> > cannot be RBF'd.
> >>
> >> My full-replace-by-fee tree ignores that. It also does preferential
> peering to
> >>
> >> ensure it's well connected with likewise peers, and thus the whole
> network.
> >>
> >>
> >> ------------------------------------------------------------
> ------------------------------------------------------------
> ---------------------------------------
> >>
> >> https://petertodd.org 'peter'[:-1]@petertodd.org
> >>
> >> bitcoin-dev mailing list
> >>
> >> bitcoin-dev@lists.linuxfoundation.org
> >>
> >> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
> >
> >
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>

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

<div dir=3D"ltr">OK.<div><br></div><div>Thank you guys for clarification.</=
div></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Wed,=
 Apr 11, 2018 at 1:00 PM, Karl-Johan Alm via bitcoin-dev <span dir=3D"ltr">=
&lt;<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_bla=
nk">bitcoin-dev@lists.linuxfoundation.org</a>&gt;</span> wrote:<br><blockqu=
ote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc s=
olid;padding-left:1ex">Thanks for clarifying!<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
On Wed, Apr 11, 2018 at 6:48 PM, ZmnSCPxj &lt;<a href=3D"mailto:ZmnSCPxj@pr=
otonmail.com">ZmnSCPxj@protonmail.com</a>&gt; wrote:<br>
&gt; Good morning Karl-Johan Alm,<br>
&gt;<br>
&gt; To clarify:<br>
&gt;<br>
&gt; Nothing prevents a miner from completely ignoring nSequence when putti=
ng transactions in blocks.<br>
&gt;<br>
&gt; Unconfirmed transactions are, by definition, not recorded in blocks.=
=C2=A0 So if there is a transaction 0xFFFFFFF nSequence and fee 1000 satosh=
i, and another conflicting transaction 0xFFFFFFF nSequence and fee 10000000=
0 satoshi, miners can include the latter one even if the first one came to =
their knowledge first, regardless nSequence.<br>
&gt;<br>
&gt; Thus, in the end &quot;full replace-by-fee&quot;, where nSequence is I=
GNORED for purposes of replace-by-fee, is expected to become the norm, and =
we should really be designing our wallets and so on so that we only trust t=
ransactions that have confirmations.<br>
&gt;<br>
&gt; The &quot;nSequence=3D0xFFFFFFFF means opt-OUT of RBF&quot; convention=
 is only followed by fullnodes running standard bitcoind.=C2=A0 Nothing pre=
vents miners from running patched bitcoind that ignores this rule, and conn=
ecting with similar peers who also ignore this rule.<br>
&gt;<br>
&gt; Regards,<br>
&gt; ZmnSCPxj<br>
&gt;<br>
&gt;<br>
&gt; Sent with ProtonMail Secure Email.<br>
&gt;<br>
&gt; =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 Origin=
al Message =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90<=
br>
&gt;<br>
&gt; On April 11, 2018 5:37 PM, Peter Todd via bitcoin-dev &lt;<a href=3D"m=
ailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.<wbr>linuxfo=
undation.org</a>&gt; wrote:<br>
&gt;<br>
&gt;&gt; On Wed, Apr 11, 2018 at 05:10:43PM +0900, Karl-Johan Alm wrote:<br=
>
&gt;&gt;<br>
&gt;&gt; &gt; On Wed, Apr 11, 2018 at 4:52 PM, Peter Todd <a href=3D"mailto=
:pete@petertodd.org">pete@petertodd.org</a> wrote:<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; &gt; Or via full replace-by-fee, which appears to be used by =
a significant minority<br>
&gt;&gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; of miners:<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; I was of the impression that final transactions (sequence=3D0=
xffffffff)<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; cannot be RBF&#39;d.<br>
&gt;&gt;<br>
&gt;&gt; My full-replace-by-fee tree ignores that. It also does preferentia=
l peering to<br>
&gt;&gt;<br>
&gt;&gt; ensure it&#39;s well connected with likewise peers, and thus the w=
hole network.<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; ------------------------------<wbr>------------------------------<=
wbr>------------------------------<wbr>------------------------------<wbr>-=
-----------------------------<wbr>---------<br>
&gt;&gt;<br>
&gt;&gt; <a href=3D"https://petertodd.org" rel=3D"noreferrer" target=3D"_bl=
ank">https://petertodd.org</a> &#39;peter&#39;[:-1]@<a href=3D"http://peter=
todd.org" rel=3D"noreferrer" target=3D"_blank">petertodd.org</a><br>
&gt;&gt;<br>
&gt;&gt; bitcoin-dev mailing list<br>
&gt;&gt;<br>
&gt;&gt; <a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-d=
ev@lists.<wbr>linuxfoundation.org</a><br>
&gt;&gt;<br>
&gt;&gt; <a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitc=
oin-dev" rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation=
.<wbr>org/mailman/listinfo/bitcoin-<wbr>dev</a><br>
&gt;<br>
&gt;<br>
______________________________<wbr>_________________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.=
<wbr>linuxfoundation.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation.<wbr>org=
/mailman/listinfo/bitcoin-<wbr>dev</a><br>
</div></div></blockquote></div><br></div>

--001a114b3aae1bb3f80569981169--