Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of petertodd.org
	designates 62.13.149.75 as permitted sender)
	client-ip=62.13.149.75; envelope-from=pete@petertodd.org;
	helo=outmail149075.authsmtp.net; 
Date: Wed, 15 May 2013 08:19:50 -0400
From: Peter Todd <pete@petertodd.org>
To: Bitcoin-Dev <bitcoin-development@lists.sourceforge.net>
Message-ID: <20130515121950.GC26020@savin>
References: <20130515113827.GB26020@savin>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="adJ1OR3c6QgCpb/j"
Content-Disposition: inline
In-Reply-To: <20130515113827.GB26020@savin>
User-Agent: Mutt/1.5.21 (2010-09-15)
Subject: Re: [Bitcoin-development] 2BTC reward for making probabalistic
 double-spending via conflicting transactions easy
Precedence: list


--adJ1OR3c6QgCpb/j
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, May 15, 2013 at 07:38:27AM -0400, Peter Todd wrote:
> So I'm offering 2BTC for anyone who comes up with a nice and easy to use
> command line tool that lets you automagically create one version of the
> transaction sending the coins to the desired recipient, and another
> version sending all the coins back to you, both with the same
> transaction inputs. In addition to creating the two versions, you need
> to find a way to broadcast them both simultaneously to different nodes
> on the network. One clever approach might be to use blockchain.info's
> raw transaction POST API, and your local Bitcoin node.

Oh, and while we're at it, a good starting point for your work would be
Gavin's spendfrom utility in the contrib/spendfrom directory in the
Bitcoin-QT respository.

Also please do keep in mind that it's much better for the community if
an attack is demonstrated first, followed by releasing the code some
time later.

--=20
'peter'[:-1]@petertodd.org


--adJ1OR3c6QgCpb/j
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQEcBAEBCAAGBQJRk31mAAoJECSBQD2l8JH7opkIAIJc8Gg9F5wXZup0eTmIsFKj
0dAApIrXIx5BCEOTg5bUR2ds5Ux6Gi0KPs9BBxi36FrEMMvl/kF4ce1ovgvQ3eZl
HHpqMcIRIjeHVoexp1i/gPQdRmrtcDo+FA5/v6XzkJMUgSxqF7smECLssdAR/2ds
X8SosCV4JvbxdpPHbbu3RsKduD2vAbcJ9bPeMafF+C1CVKWNMrbSDkSFfuoT4LCW
+uQ/6urkX28b3eLjhi+rkJ1IMpBGnTIY/O0Re5qxbBGZq8i0EKzHak6akb0imHKQ
/Ikv6yoNgCqLyjxWSRKjSr69RqNeXfEVIdgxfQEPCKfTKbH+1dxu+P3nFo8VPFw=
=Yan0
-----END PGP SIGNATURE-----

--adJ1OR3c6QgCpb/j--