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
|
Return-Path: <pete@petertodd.org>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 3F2B7AE0
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 11 Apr 2018 07:52:33 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from outmail148161.authsmtp.com (outmail148161.authsmtp.com
[62.13.148.161])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 1CA8917E
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 11 Apr 2018 07:52:31 +0000 (UTC)
Received: from mail-c245.authsmtp.com (mail-c245.authsmtp.com [62.13.128.245])
by punt22.authsmtp.com. (8.15.2/8.15.2) with ESMTP id w3B7qSRm069305;
Wed, 11 Apr 2018 08:52:28 +0100 (BST)
(envelope-from pete@petertodd.org)
Received: from petertodd.org (ec2-52-5-185-120.compute-1.amazonaws.com
[52.5.185.120]) (authenticated bits=0)
by mail.authsmtp.com (8.15.2/8.15.2) with ESMTPSA id w3B7qQxg054869
(version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO);
Wed, 11 Apr 2018 08:52:27 +0100 (BST)
(envelope-from pete@petertodd.org)
Received: from [127.0.0.1] (localhost [127.0.0.1])
by petertodd.org (Postfix) with ESMTPSA id 139A1400D0;
Wed, 11 Apr 2018 07:52:26 +0000 (UTC)
Received: by localhost (Postfix, from userid 1000)
id 73B0B203BB; Wed, 11 Apr 2018 03:52:25 -0400 (EDT)
Date: Wed, 11 Apr 2018 03:52:25 -0400
From: Peter Todd <pete@petertodd.org>
To: Karl-Johan Alm <karljohan-alm@garage.co.jp>,
Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Message-ID: <20180411075225.GG20665@savin.petertodd.org>
References: <CAO11aqjomkZcr8yeKtT5M8VUROGwz56w11UzR0pDBu333=BEPg@mail.gmail.com>
<CALJw2w6Guc6rX7A_8Nqob+w1=NKi2DfH9aj2-sg2EfgRFjDw0g@mail.gmail.com>
<CALJw2w5wfVt160uywmfOjhON8EbYkjg9bCU-6EKBO2y9TYFY5A@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
protocol="application/pgp-signature"; boundary="3xoW37o/FfUZJwQG"
Content-Disposition: inline
In-Reply-To: <CALJw2w5wfVt160uywmfOjhON8EbYkjg9bCU-6EKBO2y9TYFY5A@mail.gmail.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
X-Server-Quench: 47a0f906-3d5d-11e8-a281-9cb654bb2504
X-AuthReport-Spam: If SPAM / abuse - report it at:
http://www.authsmtp.com/abuse
X-AuthRoute: OCd2Yg0TA1ZNQRgX IjsJECJaVQIpKltL GxAVKBZePFsRUQkR
aQdMdwMUGUUGAgsB Am4bW1xeVV97W2Q7 bghPaBtcak9QXgdq
T0pMXVMcUwYaBl1g TkkeVx16cQwIcXx3 ZQhmWSFbCk16c1t+
FksACGwHMG99OWIX UV1RJFFSdQcYLB1A alQxNiYHcQ5VPz4z
GA41ejw8IwAXBilK ChgQIEkOQEENBXYm Sh8LBzkuG0JNYyQo
MyA8I1gHFU0NM0I0 WQAA
X-Authentic-SMTP: 61633532353630.1039:706
X-AuthFastPath: 0 (Was 255)
X-AuthSMTP-Origin: 52.5.185.120/25
X-AuthVirus-Status: No virus detected - but ensure you scan with your own
anti-virus system.
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,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
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 07:52:33 -0000
--3xoW37o/FfUZJwQG
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Wed, Apr 11, 2018 at 02:22:42PM +0900, Karl-Johan Alm via bitcoin-dev wr=
ote:
> Clarification on one part below:
>=20
> On Wed, Apr 11, 2018 at 2:21 PM, Karl-Johan Alm
> <karljohan-alm@garage.co.jp> wrote:
> > On Wed, Apr 11, 2018 at 5:29 AM, Maksim Solovjov via bitcoin-dev
> > <bitcoin-dev@lists.linuxfoundation.org> wrote:
> >> 1. What does it mean for a transaction ( with 0 confirmations ) to be
> >> trusted or not?
> >
> > It is trusted if (1) it is final (i.e. it can't be replaced), (2) it
> > is not in a block that was reorged out (negative confirmation count),
> > (3) the 'spend zero conf change' option is set, (4) it is in the
> > mempool, and (5) all inputs are from us.
>=20
> "can't be replaced" here means it cannot be replaced through
> conventional means. It is always possible to replace a transaction
> that has not yet been confirmed, e.g. by asking a miner to mine a
> conflicting transaction directly.
Or via full replace-by-fee, which appears to be used by a significant minor=
ity
of miners:
https://github.com/petertodd/bitcoin/tree/replace-by-fee-v0.16.0
In practice transaction replacement by the sender for any transaction is ve=
ry
easy.
--=20
https://petertodd.org 'peter'[:-1]@petertodd.org
--3xoW37o/FfUZJwQG
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
-----BEGIN PGP SIGNATURE-----
iQEcBAEBCAAGBQJazb62AAoJECSBQD2l8JH7jWgIAKkyYLWyHmUdpm3JgSlFad9n
Zm+e/xuykNCfIvVcF0XnWkG60BFPtHYCMr9YJdInchHpG+vWV0vnPSB90NBf0Vr8
Vy6zzBYVz5L1qab6O9uAO9EdBCng0e/PUJyHApQOKKjW9rJgRuU9aJU9Y7zrVzgW
ye1Vq4WoJKFjn7WdrwCXM7pV/Dfh94SeCyjJrYBM9ABl1JxXM1qLetG9iGrr0lJE
P2WdHPWwBRi515Fvzfbs0lD6omDDm6uE+4tB4ECXLWF6mhsVcMS4PwLuF1Y9/z8w
9kbvhV2fGKrrR7avIShaxyTOjzagtemY0LYWEv7lsuPP4WK6kpZCE4SIwMPB2gw=
=FhPe
-----END PGP SIGNATURE-----
--3xoW37o/FfUZJwQG--
|
