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
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <mh.in.england@gmail.com>) id 1Wf8z2-0006Ih-5s
for bitcoin-development@lists.sourceforge.net;
Tue, 29 Apr 2014 14:26:08 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.219.48 as permitted sender)
client-ip=209.85.219.48; envelope-from=mh.in.england@gmail.com;
helo=mail-oa0-f48.google.com;
Received: from mail-oa0-f48.google.com ([209.85.219.48])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Wf8z1-0003FQ-9v
for bitcoin-development@lists.sourceforge.net;
Tue, 29 Apr 2014 14:26:08 +0000
Received: by mail-oa0-f48.google.com with SMTP id m1so298694oag.21
for <bitcoin-development@lists.sourceforge.net>;
Tue, 29 Apr 2014 07:26:02 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.60.176.9 with SMTP id ce9mr2557624oec.55.1398781561915; Tue,
29 Apr 2014 07:26:01 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.76.96.180 with HTTP; Tue, 29 Apr 2014 07:26:01 -0700 (PDT)
In-Reply-To: <CAAS2fgRbGhMO+KzNQ9NhvpH6QyoaOJH-x9rDjYqEtq0R9=d7Vg@mail.gmail.com>
References: <CANEZrP3obO9rXKcX+G7bs2dd3AqEFOsO8pCUF6orrkGeZyr9Ew@mail.gmail.com>
<CAC1+kJPxwTm6qvh2GYT2XMJAPD5O4WHLOGBTRmchRmZ2wS4MSg@mail.gmail.com>
<CANEZrP2PZFVvH3oJyLW80e9W_Fa4bvqQ25E7T-ZFFuG9u-q1hQ@mail.gmail.com>
<5359E509.4080907@gmail.com>
<CANEZrP0bKe-=T5ps0myLZjo60tv2mkm3Bw0o4e-9y7zb1h5eDg@mail.gmail.com>
<535A60FE.10209@gmail.com>
<CANEZrP0y45eSVgbzXYmvYy1WEQNyd=tmC2EpZgGSB28poXSzDw@mail.gmail.com>
<535BA357.6050607@gmail.com>
<CANOOu=_T82zuV79DWZFGK0Nomhp-Y4tqOhw6ZHhCLb2uGtdR5w@mail.gmail.com>
<535CFDB4.1000200@gmail.com>
<20140428214102.GA8347@netbook.cypherspace.org>
<CANEZrP0E=i6gyJwvLZRTeKvqaVrxR69=UzJWsAqaK2=QSdtn_A@mail.gmail.com>
<CAAS2fgRbGhMO+KzNQ9NhvpH6QyoaOJH-x9rDjYqEtq0R9=d7Vg@mail.gmail.com>
Date: Tue, 29 Apr 2014 16:26:01 +0200
X-Google-Sender-Auth: 4980C0sgBpxDo1t3wbakdkkJTug
Message-ID: <CANEZrP2wDXLHDtdQPvqvz0CLRLzcsGB=uMFwWVYFq2N5CNOLrA@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Gregory Maxwell <gmaxwell@gmail.com>
Content-Type: multipart/alternative; boundary=089e0118226c1dd0fa04f82f368a
X-Spam-Score: -0.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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(mh.in.england[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1Wf8z1-0003FQ-9v
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Coinbase reallocation to discourage
Finney attacks
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, 29 Apr 2014 14:26:08 -0000
--089e0118226c1dd0fa04f82f368a
Content-Type: text/plain; charset=UTF-8
>
> These parties wouldn't generally consider themselves attackers
>
Of course not, attackers rarely do :)
But they are miners who are taking part in malicious double spending. That
makes them attackers. If miners don't exist to stop double spending, what
do they exist for?
I mean, this is fundamental. What do you think miners exist for?
--089e0118226c1dd0fa04f82f368a
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c=
cc solid;padding-left:1ex"><div class=3D"">These parties wouldn't gener=
ally consider themselves attackers</div>
</blockquote><div><br></div><div>Of course not, attackers rarely do :)</div=
><div><br></div><div>But they are miners who are taking part in malicious d=
ouble spending. That makes them attackers. If miners don't exist to sto=
p double spending, what do they exist for?</div>
<div><br></div><div>I mean, this is fundamental. What do you think miners e=
xist for?</div></div></div></div>
--089e0118226c1dd0fa04f82f368a--
|
