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
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <gavinandresen@gmail.com>) id 1S2sIY-00064J-GD
for bitcoin-development@lists.sourceforge.net;
Wed, 29 Feb 2012 22:47:02 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.212.175 as permitted sender)
client-ip=209.85.212.175; envelope-from=gavinandresen@gmail.com;
helo=mail-wi0-f175.google.com;
Received: from mail-wi0-f175.google.com ([209.85.212.175])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1S2sIX-0005m1-N5
for bitcoin-development@lists.sourceforge.net;
Wed, 29 Feb 2012 22:47:02 +0000
Received: by wibhq12 with SMTP id hq12so2733486wib.34
for <bitcoin-development@lists.sourceforge.net>;
Wed, 29 Feb 2012 14:46:55 -0800 (PST)
Received-SPF: pass (google.com: domain of gavinandresen@gmail.com designates
10.216.82.141 as permitted sender) client-ip=10.216.82.141;
Authentication-Results: mr.google.com; spf=pass (google.com: domain of
gavinandresen@gmail.com designates 10.216.82.141 as permitted
sender) smtp.mail=gavinandresen@gmail.com;
dkim=pass header.i=gavinandresen@gmail.com
Received: from mr.google.com ([10.216.82.141])
by 10.216.82.141 with SMTP id o13mr1261645wee.2.1330555615592 (num_hops
= 1); Wed, 29 Feb 2012 14:46:55 -0800 (PST)
MIME-Version: 1.0
Received: by 10.216.82.141 with SMTP id o13mr1018517wee.2.1330555615521; Wed,
29 Feb 2012 14:46:55 -0800 (PST)
Received: by 10.223.121.197 with HTTP; Wed, 29 Feb 2012 14:46:55 -0800 (PST)
In-Reply-To: <CAPBPUnqgV_hHYwFoB_1qXMvEaE1pM0vm8=V=AKe2n-rPFzz+mQ@mail.gmail.com>
References: <CAPg+sBhb+gYMwp1OJuCHYt5=BU63=YBWOFaLLthHBkN_U-scaA@mail.gmail.com>
<CAPBPUnqgV_hHYwFoB_1qXMvEaE1pM0vm8=V=AKe2n-rPFzz+mQ@mail.gmail.com>
Date: Wed, 29 Feb 2012 17:46:55 -0500
Message-ID: <CABsx9T1YbFLcuCLbZZvSJGPy9k0PRgWttOp-KPUW+99XSYTkQQ@mail.gmail.com>
From: Gavin Andresen <gavinandresen@gmail.com>
To: Ben Reeves <support@pi.uk.com>
Content-Type: text/plain; charset=ISO-8859-1
X-Spam-Score: -1.4 (-)
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
(gavinandresen[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
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
0.2 AWL AWL: From: address is in the auto white-list
X-Headers-End: 1S2sIX-0005m1-N5
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Duplicate transactions vulnerability
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: Wed, 29 Feb 2012 22:47:02 -0000
On Wed, Feb 29, 2012 at 5:05 PM, Ben Reeves <support@pi.uk.com> wrote:
> A malicious miner can produce a duplicate coinbase which the majority
> of clients will accept but the majority of hashing power won't.
> Spending the coinbase output after....
That can't happen until the coinbase matures, which takes 100 blocks.
And it won't mature because a majority of hashing power is rejecting
it, right?
--
--
Gavin Andresen
|
