From: Thomas Zander <thomas@thomaszander.se>
To: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Mempool "Expected Byte Stay" policy
Date: Wed, 15 Jul 2015 21:18:49 +0200 [thread overview]
Message-ID: <2272402.KPsXmgHuuj@coldstorage> (raw)
In-Reply-To: <55A5A837.1090203@thinlink.com>
On Tuesday 14. July 2015 17.24.23 Tom Harding via bitcoin-dev wrote:
> Rule 2: A transaction and its dependents are evicted on its 2-hour
> anniversary, whether space is required or not
Instead of 2 hours, why not a number of blocks?
--
Thomas Zander
next prev parent reply other threads:[~2015-07-15 19:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-15 0:24 [bitcoin-dev] Mempool "Expected Byte Stay" policy Tom Harding
2015-07-15 19:18 ` Thomas Zander [this message]
2015-07-15 23:15 ` Tom Harding
2015-07-16 9:38 ` Thomas Zander
2015-07-16 16:50 ` Tom Harding
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=2272402.KPsXmgHuuj@coldstorage \
--to=thomas@thomaszander.se \
--cc=bitcoin-dev@lists.linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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