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; 
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)
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: [Bitcoin-development]  replace-by-fee v0.9.3 release
Precedence: list


--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--