summaryrefslogtreecommitdiff
path: root/3c/6a4f2e01c33d53927c7f2f3c8aeb99023238de
blob: e5e7bc30af582c6c189e92f6c6d32b7de5296976 (plain)
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
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
	helo=mx.sourceforge.net)
	by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <pete@petertodd.org>) id 1UemGr-0004LQ-Md
	for bitcoin-development@lists.sourceforge.net;
	Tue, 21 May 2013 13:06:29 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of petertodd.org
	designates 62.13.148.100 as permitted sender)
	client-ip=62.13.148.100; envelope-from=pete@petertodd.org;
	helo=outmail148100.authsmtp.co.uk; 
Received: from outmail148100.authsmtp.co.uk ([62.13.148.100])
	by sog-mx-3.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
	id 1UemGp-0006UZ-Uz for bitcoin-development@lists.sourceforge.net;
	Tue, 21 May 2013 13:06:29 +0000
Received: from mail-c232.authsmtp.com (mail-c232.authsmtp.com [62.13.128.232])
	by punt5.authsmtp.com (8.14.2/8.14.2/Kp) with ESMTP id
	r4LD6L0K058200; Tue, 21 May 2013 14:06:21 +0100 (BST)
Received: from tilt (dhcp184-48-74-214.hil-sckmthx.sjc.wayport.net
	[184.48.74.214]) (authenticated bits=128)
	by mail.authsmtp.com (8.14.2/8.14.2/) with ESMTP id r4LD6Ew8027181
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO);
	Tue, 21 May 2013 14:06:17 +0100 (BST)
Date: Tue, 21 May 2013 06:06:13 -0700
From: Peter Todd <pete@petertodd.org>
To: Robert Backhaus <robbak@robbak.com>
Message-ID: <20130521130613.GB27580@tilt>
References: <519AC3A8.1020306@quinnharris.me>
	<CA+i0-i_+Tes+ePRqmDGEXDQ_L=S5y8gHBKk77zaLgTGOS3OMyA@mail.gmail.com>
	<CAPg+sBjmXyLkgfwzC8h+ZFkmyUf6nzbGo0oAWR9nsJOTOfOXEg@mail.gmail.com>
	<CANEZrP1inofLkfcb3q+_yBd6ZX0OGs-mNbcmu9+ECwn5wVD7jw@mail.gmail.com>
	<CA+i0-i-8DFUBLpjtpBGrarH72vqX5FgQGkGUYb-Zz7efHehuwA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="jy6Sn24JjFx/iggw"
Content-Disposition: inline
In-Reply-To: <CA+i0-i-8DFUBLpjtpBGrarH72vqX5FgQGkGUYb-Zz7efHehuwA@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-Server-Quench: 3a128255-c217-11e2-b10b-0025903375e2
X-AuthReport-Spam: If SPAM / abuse - report it at:
	http://www.authsmtp.com/abuse
X-AuthRoute: OCd2Yg0TA1ZNQRgX IjsJECJaVQIpKltL GxAVKBZePFsRUQkR
	aAdMdAMUFVQNAgsB AmUbWlBeUFt7WGs7 agJVcwFVfE1KQQdr
	VFdMSlVNFUsqBWB1 AGtZWhlwcAROeTB3 bURlEHMKXUZyd0N4
	Xx1WFGobZGY1an1N UUAKagNUcgZDfhxG bVUqVj1vNG8XDQg5
	AwQ0PjZ0MThBJSBS WgQAK04nCWoMAzQ4 Slg5BTgpEQUjQDky IR0tI0IdG0B5
X-Authentic-SMTP: 61633532353630.1019:706
X-AuthFastPath: 0 (Was 255)
X-AuthSMTP-Origin: 184.48.74.214/587
X-AuthVirus-Status: No virus detected - but ensure you scan with your own
	anti-virus system.
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 SPF_PASS               SPF: sender matches SPF record
X-Headers-End: 1UemGp-0006UZ-Uz
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Double Spend Notification
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: Tue, 21 May 2013 13:06:29 -0000


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

On Tue, May 21, 2013 at 01:39:30PM +1000, Robert Backhaus wrote:
> That's good - what I had taken away from the replace-by-fee discussions w=
as
> that it was finally decided.
>=20
> My opinion is that we should be doing what we can to make 0-confs as
> reliable as possible - which will always be 'not very', but a solid system
> to notify on attempted double-spends is a good start.
>=20
> I'd like to know how Peter Todd's experiment with the 2BTC reward has gon=
e.

piuk wrote a double-spender that I think meets the criteria for the
reward: https://blockchain.info/create-double-spend

I'll get a chance to test it properly when I'm back from vacation, but
looks like he's getting the 2BTC. If it does work as intended I'm also
planning on doing a demo/video at the next Toronto Bitcoin Meetup to
demonstrate the attack in a real-life exchange.

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

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

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

iQEcBAEBCAAGBQJRm3FAAAoJEH+rEUJn5PoEkiUH/jQQFcZXAp5B+s9kRGSKZqsY
Cen5/w/YW7v+bcLBryn+o72zPPVsQI8PdYpPBBs5WNJFBy0Kfnup/RG2FjBDSKow
DkiN/0PqK3j2m6uH5RvJkOluXWRXRtzXxz0mGTYWNPWjCTOOKZ17d2kWZTTOywjt
uRP1iCUYthz/fpSR2f8PrphTyL/Z8WyK49VFy1Fa78Xv87Ph9xDZzQGbfHt69vAJ
BUnO5bI7f6tglNiJuMV9v5oFRegNwM3d7hnEXCGYosq8YRSjkF09ab+fNjGj5p/V
ofg9AUwDKKVG+7zlbbVeEhpKf3Uf8Jns+xG204twiG6v0xhTYQ8NCmMdak/pxEw=
=+5d8
-----END PGP SIGNATURE-----

--jy6Sn24JjFx/iggw--