From: "Jorge Timón" <timon.elviejo@gmail•com>
To: Bitcoin Development <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Large backlog of transactions building up?
Date: Tue, 25 Sep 2012 19:34:50 +0200 [thread overview]
Message-ID: <CAGQP0AHdmyMhrOA1mMqjxobu8S0r6OnvducV7H=HFaiv-PR+rw@mail.gmail.com> (raw)
In-Reply-To: <CANEZrP03R_6nQQ-_uxdF++g-ON4ynsNBTDFqmVt2ZnLy49GqZg@mail.gmail.com>
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?
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?
next prev parent reply other threads:[~2012-09-25 17:34 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 [this message]
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='CAGQP0AHdmyMhrOA1mMqjxobu8S0r6OnvducV7H=HFaiv-PR+rw@mail.gmail.com' \
--to=timon.elviejo@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