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
|
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 <shadders.del@gmail.com>) id 1R0xVi-0002dQ-KL
for bitcoin-development@lists.sourceforge.net;
Tue, 06 Sep 2011 15:24:26 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.216.182 as permitted sender)
client-ip=209.85.216.182; envelope-from=shadders.del@gmail.com;
helo=mail-qy0-f182.google.com;
Received: from mail-qy0-f182.google.com ([209.85.216.182])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1R0xVh-0001Em-Ql
for bitcoin-development@lists.sourceforge.net;
Tue, 06 Sep 2011 15:24:26 +0000
Received: by qyk9 with SMTP id 9so3868678qyk.13
for <bitcoin-development@lists.sourceforge.net>;
Tue, 06 Sep 2011 08:24:20 -0700 (PDT)
Received: by 10.52.70.239 with SMTP id p15mr1238923vdu.67.1315322660366;
Tue, 06 Sep 2011 08:24:20 -0700 (PDT)
Received: from [10.1.1.50] (155.88-67-202.dynamic.dsl.syd.iprimus.net.au
[202.67.88.155])
by mx.google.com with ESMTPS id q5sm300317vdu.23.2011.09.06.08.24.18
(version=SSLv3 cipher=OTHER); Tue, 06 Sep 2011 08:24:19 -0700 (PDT)
Message-ID: <4E663B1B.7000503@gmail.com>
Date: Wed, 07 Sep 2011 01:24:11 +1000
From: Steve <shadders.del@gmail.com>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US;
rv:1.9.2.21) Gecko/20110831 Thunderbird/3.1.13
MIME-Version: 1.0
To: Gavin Andresen <gavinandresen@gmail.com>
References: <CABsx9T0kBPJfdrKYcp0qHxDRdhYYbAwQ7wuwkwUF97rgSDNnKQ@mail.gmail.com>
In-Reply-To: <CABsx9T0kBPJfdrKYcp0qHxDRdhYYbAwQ7wuwkwUF97rgSDNnKQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: -1.3 (-)
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
(shadders.del[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.3 AWL AWL: From: address is in the auto white-list
X-Headers-End: 1R0xVh-0001Em-Ql
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Many-output transactions in the main chain
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: shadders.del@gmail.com
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, 06 Sep 2011 15:24:26 -0000
Is this the ArtForz solidcoin 'attack'?
On 07/09/11 01:21, Gavin Andresen wrote:
> Somebody has been inserting transactions with lots of outputs into the
> main bitcoin block chain:
> http://blockexplorer.com/block/0000000000000305f98ffbe1db8445ce847fb9a924551945b465386c828f136f
>
> Their next step will be creating transactions with thousands of inputs
> from those transactions. The result will be lots of excessive disk
> space usage.
>
> The fix is this patch:
> https://github.com/bitcoin/bitcoin/pull/491
>
> Suggestions on the best way to let merchants, miners, and pools know
> about the potential problem?
> I hate to take time away from the 0.4 release to re-spin 0.3.24 with
> the patch, but we may have to.
>
|
