Subject: Re: [Bitcoin-development] Bitcoin TX fill-or-kill deterministic behavior

From: Jeff Garzik <[email-masked]>
Date: Sun, 15 Apr 2012 11:17:04 -0400

2012/4/15 Jorge Timón <[email-masked]>:
> On 4/12/12, Jeff Garzik <[email-masked]> 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.
[email-masked]