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
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <pete@petertodd.org>) id 1XY6pl-0000Vv-Jd
for bitcoin-development@lists.sourceforge.net;
Sun, 28 Sep 2014 05:15:45 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of petertodd.org
designates 62.13.149.112 as permitted sender)
client-ip=62.13.149.112; envelope-from=pete@petertodd.org;
helo=outmail149112.authsmtp.co.uk;
Received: from outmail149112.authsmtp.co.uk ([62.13.149.112])
by sog-mx-4.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
id 1XY6pj-0002EV-IM for bitcoin-development@lists.sourceforge.net;
Sun, 28 Sep 2014 05:15:45 +0000
Received: from mail-c235.authsmtp.com (mail-c235.authsmtp.com [62.13.128.235])
by punt17.authsmtp.com (8.14.2/8.14.2/) with ESMTP id s8S5FaM9029384;
Sun, 28 Sep 2014 06:15:36 +0100 (BST)
Received: from savin.petertodd.org (75-119-251-161.dsl.teksavvy.com
[75.119.251.161]) (authenticated bits=128)
by mail.authsmtp.com (8.14.2/8.14.2/) with ESMTP id s8S5FVjo047997
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO);
Sun, 28 Sep 2014 06:15:34 +0100 (BST)
Date: Sun, 28 Sep 2014 01:15:53 -0400
From: Peter Todd <pete@petertodd.org>
To: Tom Harding <tomh@thinlink.com>
Message-ID: <20140928051553.GB11287@savin.petertodd.org>
References: <CACq0ZD4Ki=7Tba_2UhmuH-dPCbOnfXrJRcLPc+fP6Uur4FpG_A@mail.gmail.com>
<1447373.AzvO89eGJS@crushinator>
<CACq0ZD55G7sAXuu-UxoVJuuk1rwxKKwAPg4qkRoTreD1X2fc9Q@mail.gmail.com>
<6165581.aoAyGZkGge@crushinator>
<CACq0ZD6sMHW6QEHHqDkaZwEwyfuk1CUjb0BRhzt3B+g+8CoP5A@mail.gmail.com>
<542778B0.7090202@thinlink.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
protocol="application/pgp-signature"; boundary="B4IIlcmfBL/1gGOG"
Content-Disposition: inline
In-Reply-To: <542778B0.7090202@thinlink.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-Server-Quench: 79d4c366-46ce-11e4-b396-002590a15da7
X-AuthReport-Spam: If SPAM / abuse - report it at:
http://www.authsmtp.com/abuse
X-AuthRoute: OCd2Yg0TA1ZNQRgX IjsJECJaVQIpKltL GxAVKBZePFsRUQkR
aQdMdAoUC1AEAgsB AmIbW1JeUVh7Wmc7 bA9PbARUfEhLXhtr
VklWR1pVCwQmQhRi A2h4CEZycwJPcXk+ ZERjWngVW00ucRV+
REhJEWtVMHphaTUb TRJbfgVJcANIexZF O1F6ACIKLw51Pz4z
GA41ejw8IzhbLzxQ TwcRGBoITF4PFzUx AhoTWDsiEAUbH2Ni
aUduMFMYEU8KPy0A
X-Authentic-SMTP: 61633532353630.1023:706
X-AuthFastPath: 255
X-AuthSMTP-Origin: 75.119.251.161/587
X-Spam-Score: -1.5 (-)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
-0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/,
no trust [62.13.149.112 listed in list.dnswl.org]
-0.0 SPF_PASS SPF: sender matches SPF record
X-Headers-End: 1XY6pj-0002EV-IM
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: [Bitcoin-development] replace-by-fee v0.9.3 release
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Sun, 28 Sep 2014 05:15:45 -0000
--B4IIlcmfBL/1gGOG
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Sat, Sep 27, 2014 at 07:55:44PM -0700, Tom Harding wrote:
> On 9/25/2014 7:37 PM, Aaron Voisine wrote:
> > Of course you wouldn't want nodes to propagate alerts without
> > independently verifying them
> How would a node independently verify a double-spend alert, other than=20
> by having access to an actual signed double-spend?
>=20
> #4570 relays the first double-spend AS an alert. Running this branch on=
=20
> mainnet, I have been keeping a live list of relayed double-spend=20
> transactions at http://respends.thinlink.com
Speaking of, I ported my replace-by-fee branch the recent v0.9.3
release: https://github.com/petertodd/bitcoin/tree/replace-by-fee-v0.9.3
I actually ported it a few days ago; that release has been running on a
half-dozen or so nodes right now for a few days with no issues.
The v0.9.3 release's scriptSig size limit increase adds a new category
of double-spending exploit. I'm not going to get time to add that
exploit to my replace-by-fee toolkit(1) for at least another week or so
though - pull-reqs accepted.
1) https://github.com/petertodd/replace-by-fee-tools
--=20
'peter'[:-1]@petertodd.org
0000000000000000084778cc7b7394a48d65c9451a59dcf98d0f1e1078f39c3a
--B4IIlcmfBL/1gGOG
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
-----BEGIN PGP SIGNATURE-----
iQGrBAEBCACVBQJUJ5mEXhSAAAAAABUAQGJsb2NraGFzaEBiaXRjb2luLm9yZzAw
MDAwMDAwMDAwMDAwMDAwODQ3NzhjYzdiNzM5NGE0OGQ2NWM5NDUxYTU5ZGNmOThk
MGYxZTEwNzhmMzljM2EvFIAAAAAAFQARcGthLWFkZHJlc3NAZ251cGcub3JncGV0
ZUBwZXRlcnRvZC5vcmcACgkQJIFAPaXwkfsC1wgAojyu1RaKARKcd5THFyO/GQ9G
7oT/Bfz8tnKwbTyZBpk9x3ZRMwDX1wOTtuYOxA5Awp/ZYeYtit68XXcvLDGCaCXa
Qaql4mbH3egtV4MgprEsZxUl3WQMuzqs6Eqm9uOdKTXDEGJeymlWxY2WlzHrIfPc
bAhM5BhiAOchi995SA8Qm9QRXYV3JE3vK5iyPIKqIcQzrQ5P6TInZ3+E1oNp8nEL
qNghUCM1j5PYB0waEPRzzW5fa29NkmoeJEUJkPAHwrPRC1Yajsp4lXNxza+ohQea
7ke7OU6St9s8cpqF3xqQV+e3olfUR/8MrSL4QlfNdOt5B1WUKRutIuk26UCgEg==
=XsXx
-----END PGP SIGNATURE-----
--B4IIlcmfBL/1gGOG--
|
