[Bitcoin-development] Bitcoin TX fill-or-kill deterministic behavior

Jorge Timón timon.elviejo at gmail.com
Sun Apr 15 10:54:23 UTC 2012

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

Another question, aren't different peers going to get different H1 for
the same tx?

More information about the bitcoin-dev mailing list