From: Gavin Andresen <gavinandresen@gmail•com>
To: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: [Bitcoin-development] Many-output transactions in the main chain
Date: Tue, 6 Sep 2011 11:21:52 -0400 [thread overview]
Message-ID: <CABsx9T0kBPJfdrKYcp0qHxDRdhYYbAwQ7wuwkwUF97rgSDNnKQ@mail.gmail.com> (raw)
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
next reply other threads:[~2011-09-06 15:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-06 15:21 Gavin Andresen [this message]
2011-09-06 15:24 ` Steve
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CABsx9T0kBPJfdrKYcp0qHxDRdhYYbAwQ7wuwkwUF97rgSDNnKQ@mail.gmail.com \
--to=gavinandresen@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox