Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
	helo=mx.sourceforge.net)
	by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <gavinandresen@gmail.com>) id 1R0xTQ-0004aG-V7
	for bitcoin-development@lists.sourceforge.net;
	Tue, 06 Sep 2011 15:22:05 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.161.47 as permitted sender)
	client-ip=209.85.161.47; envelope-from=gavinandresen@gmail.com;
	helo=mail-fx0-f47.google.com; 
Received: from mail-fx0-f47.google.com ([209.85.161.47])
	by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1R0xTL-0005vs-4z
	for bitcoin-development@lists.sourceforge.net;
	Tue, 06 Sep 2011 15:22:04 +0000
Received: by fxg11 with SMTP id 11so6312873fxg.34
	for <bitcoin-development@lists.sourceforge.net>;
	Tue, 06 Sep 2011 08:21:52 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.46.90 with SMTP id i26mr1609086faf.83.1315322512887; Tue,
	06 Sep 2011 08:21:52 -0700 (PDT)
Received: by 10.152.22.130 with HTTP; Tue, 6 Sep 2011 08:21:52 -0700 (PDT)
Date: Tue, 6 Sep 2011 11:21:52 -0400
Message-ID: <CABsx9T0kBPJfdrKYcp0qHxDRdhYYbAwQ7wuwkwUF97rgSDNnKQ@mail.gmail.com>
From: Gavin Andresen <gavinandresen@gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: text/plain; charset=ISO-8859-1
X-Spam-Score: -1.6 (-)
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
X-Headers-End: 1R0xTL-0005vs-4z
Subject: [Bitcoin-development] Many-output transactions in the main chain
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, 06 Sep 2011 15:22:05 -0000

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.

-- 
--
Gavin Andresen