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
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <support@pi.uk.com>) id 1S2sVt-0004lr-7X
for bitcoin-development@lists.sourceforge.net;
Wed, 29 Feb 2012 23:00:49 +0000
Received: from mail-qy0-f175.google.com ([209.85.216.175])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-MD5:128)
(Exim 4.76) id 1S2sVs-0004kr-Fj
for bitcoin-development@lists.sourceforge.net;
Wed, 29 Feb 2012 23:00:49 +0000
Received: by qcso7 with SMTP id o7so1980442qcs.34
for <bitcoin-development@lists.sourceforge.net>;
Wed, 29 Feb 2012 15:00:43 -0800 (PST)
Received-SPF: pass (google.com: domain of support@pi.uk.com designates
10.224.196.66 as permitted sender) client-ip=10.224.196.66;
Authentication-Results: mr.google.com;
spf=pass (google.com: domain of support@pi.uk.com
designates 10.224.196.66 as permitted sender)
smtp.mail=support@pi.uk.com
Received: from mr.google.com ([10.224.196.66])
by 10.224.196.66 with SMTP id ef2mr4436319qab.64.1330556443116
(num_hops = 1); Wed, 29 Feb 2012 15:00:43 -0800 (PST)
MIME-Version: 1.0
Received: by 10.224.196.66 with SMTP id ef2mr3701741qab.64.1330556442894; Wed,
29 Feb 2012 15:00:42 -0800 (PST)
Received: by 10.229.226.139 with HTTP; Wed, 29 Feb 2012 15:00:42 -0800 (PST)
X-Originating-IP: [81.187.238.52]
In-Reply-To: <CABsx9T1YbFLcuCLbZZvSJGPy9k0PRgWttOp-KPUW+99XSYTkQQ@mail.gmail.com>
References: <CAPg+sBhb+gYMwp1OJuCHYt5=BU63=YBWOFaLLthHBkN_U-scaA@mail.gmail.com>
<CAPBPUnqgV_hHYwFoB_1qXMvEaE1pM0vm8=V=AKe2n-rPFzz+mQ@mail.gmail.com>
<CABsx9T1YbFLcuCLbZZvSJGPy9k0PRgWttOp-KPUW+99XSYTkQQ@mail.gmail.com>
Date: Wed, 29 Feb 2012 23:00:42 +0000
Message-ID: <CAPBPUnp61tCr5yVa36OGoqmO83hOJitnWJDyW3SihXyxy_FbYg@mail.gmail.com>
From: Ben Reeves <support@pi.uk.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQlbNWuYLEjLBzYqopmRAHS2mQHVBTSOw/bkrfGjDQzbSJ/x3oyKea4SBfJ2LfGZcbnGLRGy
X-Spam-Score: -1.2 (-)
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.2 AWL AWL: From: address is in the auto white-list
X-Headers-End: 1S2sVs-0004kr-Fj
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 23:00:49 -0000
I'm not sure. What if they use a coinbase of a block that has already matured?
On Wed, Feb 29, 2012 at 10:46 PM, Gavin Andresen
<gavinandresen@gmail.com> wrote:
> 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
|
