2012/4/15 Jorge Timón <timon.elvi...@gmail.com>: > On 4/12/12, Jeff Garzik <jgar...@exmulti.com> wrote: >> 1. N = 1 or 2 or whatever the community prefers. Ideally enough time >> for a third-tier miner, mining strange TXs, finds a block. >> 2. H1 = height of block chain, when a TX is received >> 3. H2 = H1 + (144 * N) >> 4. If block chain height reaches H2, and TX has not made it into a >> block, drop TX from memory pool > > Why not just adding a field expiration_block = H2? > It seems more explicit and flexible than using a 144 * N constant. > You're changing the protocol anyway, right?
No, not changing the protocol. Further, adding a field to TX would imply the client needed to rewrite the TX for each retransmit, changing the hash. Not good at all. > Another question, aren't different peers going to get different H1 for > the same tx? Typically no, because 99.9% of TX's make it throughout the network in seconds. But yes it is possible, just like it is possible today to receive a TX at various times. -- Jeff Garzik exMULTI, Inc. jgar...@exmulti.com ------------------------------------------------------------------------------ For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2 _______________________________________________ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
