[Bitcoin-development] Large backlog of transactions building up?

Jorge Timón timon.elviejo at gmail.com
Tue Sep 25 17:34:50 UTC 2012

On 9/23/12, Jeff Garzik <jgarzik at 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 at 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?

More information about the bitcoin-dev mailing list