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: <ZmnSCPxj@protonmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 3E5A5D37
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 11 Apr 2018 09:48:49 +0000 (UTC)
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6
Received: from mail5.protonmail.ch (mail5.protonmail.ch [185.70.40.28])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 7381262A
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 11 Apr 2018 09:48:48 +0000 (UTC)
Date: Wed, 11 Apr 2018 05:48:39 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com;
s=default; t=1523440123;
bh=6goPzvx1cktQSvA0aUuCcoTcNR59GWShEXDOy7GyH+o=;
h=Date:To:From:Cc:Reply-To:Subject:In-Reply-To:References:
Feedback-ID:From;
b=eqD3RPjfz+Xs4be41Upg6evXGwA0peEXyzpfVVjXDbyeJkkI942AEF9K37U2GFpB/
N0E+RmoqNkI2rZinY5yQqoB6+gcMYFwKhJjO1/uoXND6pTMndVmUpzybCIiJyQakde
wVoAMkB3gMCc8CjFl7S3nnk95vIDtRBzT0EsieZA=
To: Peter Todd <pete@petertodd.org>,
Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
From: ZmnSCPxj <ZmnSCPxj@protonmail.com>
Reply-To: ZmnSCPxj <ZmnSCPxj@protonmail.com>
Message-ID: <W-3_0a0Wp9HoQBvu-eGzXlwpj63Kk4kAGWECRax6CqdvML961niOTYkq60sv381rS-ffpQGG-apaTtvHkjkobNVlyXAG_WSekXevGmaOS5Q=@protonmail.com>
In-Reply-To: <20180411093724.GA21441@savin.petertodd.org>
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>
Feedback-ID: el4j0RWPRERue64lIQeq9Y2FP-mdB86tFqjmrJyEPR9VAtMovPEo9tvgA0CrTsSHJeeyPXqnoAu6DN-R04uJUg==:Ext:ProtonMail
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Spam-Status: No, score=-2.2 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, FROM_LOCAL_NOVOWEL,
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: Wed, 11 Apr 2018 14:08:12 +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 09:48:49 -0000
Good morning Karl-Johan Alm,
To clarify:
Nothing prevents a miner from completely ignoring nSequence when putting tr=
ansactions in blocks.
Unconfirmed transactions are, by definition, not recorded in blocks. So if=
there is a transaction 0xFFFFFFF nSequence and fee 1000 satoshi, and anoth=
er conflicting transaction 0xFFFFFFF nSequence and fee 100000000 satoshi, m=
iners can include the latter one even if the first one came to their knowle=
dge first, regardless nSequence.
Thus, in the end "full replace-by-fee", where nSequence is IGNORED for purp=
oses of replace-by-fee, is expected to become the norm, and we should reall=
y be designing our wallets and so on so that we only trust transactions tha=
t have confirmations.
The "nSequence=3D0xFFFFFFFF means opt-OUT of RBF" convention is only follow=
ed by fullnodes running standard bitcoind. Nothing prevents miners from ru=
nning patched bitcoind that ignores this rule, and connecting with similar =
peers who also ignore this rule.
Regards,
ZmnSCPxj
=E2=80=8BSent with ProtonMail Secure Email.=E2=80=8B
=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 Original Me=
ssage =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.li=
nuxfoundation.org> wrote:
> On Wed, Apr 11, 2018 at 05:10:43PM +0900, Karl-Johan Alm wrote:
>=20
> > On Wed, Apr 11, 2018 at 4:52 PM, Peter Todd pete@petertodd.org wrote:
> >=20
> > > Or via full replace-by-fee, which appears to be used by a significant=
minority
> > >=20
> > > of miners:
> >=20
> > I was of the impression that final transactions (sequence=3D0xffffffff)
> >=20
> > cannot be RBF'd.
>=20
> My full-replace-by-fee tree ignores that. It also does preferential peeri=
ng to
>=20
> ensure it's well connected with likewise peers, and thus the whole networ=
k.
>=20
>=20
> -------------------------------------------------------------------------=
---------------------------------------------------------------------------=
-----------
>=20
> https://petertodd.org 'peter'[:-1]@petertodd.org
>=20
> bitcoin-dev mailing list
>=20
> bitcoin-dev@lists.linuxfoundation.org
>=20
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
|
