From: Gregory Maxwell <gmaxwell@gmail•com>
To: Jeff Garzik <jgarzik@exmulti•com>
Cc: Bitcoin Development <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Large backlog of transactions building up?
Date: Sun, 23 Sep 2012 16:44:55 -0400 [thread overview]
Message-ID: <CAAS2fgR7yiyTWyuwAqxsnAb-xv9bmBFUxDwJhEkRH1PCP=pzJw@mail.gmail.com> (raw)
In-Reply-To: <CA+8xBpen9o3Oji0ePsbU-ZQCSpFO+tAZt63LaOsR30KULYbUhQ@mail.gmail.com>
On Sun, Sep 23, 2012 at 4:30 PM, Jeff Garzik <jgarzik@exmulti•com> wrote:
> Yeah, my public nodes currently have 2200+ Over time, it gets
> cluttered naturally due to the disconnect between what miners mine and
> what relayers relay.
Right, this disconnect is why simple scalar measures of mempool size
aren't terribly informative.
There are bursts of weird transactions (e.g. someone was flooding zero
value txn a few weeks ago; before that there were some enormous series
of double-spend induced orphans), and other sustained loads that quite
a few miners are intentionally excluding.
> No one has strenuously argued against this, so I suppose it is down to
> writing a patch, and coming up with a good number we (as a network)
> can agree upon.
Sounds good— my only concern is that nodes will repeat their own
transactions but not the unconfirmed parents. So being more aggressive
can turn otherwise valid transactions into orphans.
Would there be value in an archive-mempool which is only checked when
you receive an orphan transaction?
I would point out that you can't _KNOW_ a txn will disappear. Someone
else could happily reannounce it. (I know you know this; but it's good
to be clear on that point when we talk about it!)
next prev parent reply other threads:[~2012-09-23 20:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-23 12:12 Mike Hearn
2012-09-23 20:30 ` Jeff Garzik
2012-09-23 20:44 ` Gregory Maxwell [this message]
2012-09-23 21:54 ` Mike Hearn
2012-09-25 17:34 ` Jorge Timón
2012-09-25 17:52 ` Gregory Maxwell
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='CAAS2fgR7yiyTWyuwAqxsnAb-xv9bmBFUxDwJhEkRH1PCP=pzJw@mail.gmail.com' \
--to=gmaxwell@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=jgarzik@exmulti$(echo .)com \
/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