From: Gregory Maxwell <gmaxwell@gmail•com>
To: "Jorge Timón" <timon.elviejo@gmail•com>
Cc: Bitcoin Development <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Large backlog of transactions building up?
Date: Tue, 25 Sep 2012 13:52:10 -0400 [thread overview]
Message-ID: <CAAS2fgRmS0ssKJvJsrhpbmj4awViexhQbQJB-TUU1gUQ8TzOeg@mail.gmail.com> (raw)
In-Reply-To: <CAGQP0AHdmyMhrOA1mMqjxobu8S0r6OnvducV7H=HFaiv-PR+rw@mail.gmail.com>
On Tue, Sep 25, 2012 at 1:34 PM, Jorge Timón <timon.elviejo@gmail•com> wrote:
> On 9/23/12, Jeff Garzik <jgarzik@exmulti•com> wrote:
>> - provides a deterministic lifetime for a TX; if you KNOW a TX will
>> disappear 144 blocks (24 hours) after you stop transmitting, then it
>> is probably safe to initiate recovery procedures and perhaps revise
>> the transaction
>> - prevents zombie TXs from littering memory... they hang around,
>> wasting resources, but never get confirmed
>
> I don't understand. Can the chain enforce this number?
> Why can't clients delete all those transactions right now?
This is discussion about transactions which are not in the chain yet.
> On 9/23/12, Gregory Maxwell <gmaxwell@gmail•com> wrote:
>> 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.
>
> Why clients store transactions that don't obey the current rules of
> the chain at all?
The double spending transaction is not stored— which is, in fact, the
problem which creates these huge chain. When a transaction depending
on the doublespend is received we do not know its parent (because we
dropped it because it was a rule violation) so we keep it around as an
orphan hoping its parent arrives.
The software could maintain a cache of rejected txids to consult for
orphan txn's parents, but it would need to be dropped any time there
is a reorg so I don't know how useful it would be.
prev parent reply other threads:[~2012-09-25 17:52 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
2012-09-23 21:54 ` Mike Hearn
2012-09-25 17:34 ` Jorge Timón
2012-09-25 17:52 ` Gregory Maxwell [this message]
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=CAAS2fgRmS0ssKJvJsrhpbmj4awViexhQbQJB-TUU1gUQ8TzOeg@mail.gmail.com \
--to=gmaxwell@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=timon.elviejo@gmail$(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