On 9/23/12, Jeff Garzik <jgar...@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 <gmaxw...@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? ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
