From: "Jorge Timón" <timon.elviejo@gmail•com>
To: Jeff Garzik <jgarzik@exmulti•com>
Cc: Bitcoin Development <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Bitcoin TX fill-or-kill deterministic behavior
Date: Sun, 15 Apr 2012 12:54:23 +0200 [thread overview]
Message-ID: <CAGQP0AGbLYZYwKGb0AHOPx3BadBQ399A67ntEo98mpm=kKgZ+g@mail.gmail.com> (raw)
In-Reply-To: <CA+8xBpc5CZ9Sx4MwPdeS0-5frnV9B+mJ5OwcPoUVrygTawiJBg@mail.gmail.com>
On 4/12/12, Jeff Garzik <jgarzik@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?
next prev parent reply other threads:[~2012-04-15 10:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-12 18:38 Jeff Garzik
2012-04-12 19:19 ` Alan Reiner
2012-04-12 19:26 ` Jeff Garzik
2012-04-13 8:35 ` Andy Parkins
2012-04-13 10:04 ` Mike Hearn
2012-04-13 16:41 ` Jeff Garzik
2012-04-14 15:13 ` Mike Hearn
2012-04-14 20:20 ` Jeff Garzik
2012-04-14 21:27 ` Pieter Wuille
2012-04-14 22:49 ` Jeff Garzik
2012-04-15 8:12 ` Andreas Schildbach
2012-04-15 10:54 ` Jorge Timón [this message]
2012-04-15 15:17 ` Jeff Garzik
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAGQP0AGbLYZYwKGb0AHOPx3BadBQ399A67ntEo98mpm=kKgZ+g@mail.gmail.com' \
--to=timon.elviejo@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=jgarzik@exmulti$(echo .)com \
--cc=jtimonmv@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox