From: Thomas Zander <thomas@thomaszander•se>
To: bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] Mempool "Expected Byte Stay" policy
Date: Thu, 16 Jul 2015 11:38:54 +0200 [thread overview]
Message-ID: <2509294.8eWsy7oNj2@coldstorage> (raw)
In-Reply-To: <55A6E98C.3090307@thinlink.com>
On Wednesday 15. July 2015 16.15.24 Tom Harding via bitcoin-dev wrote:
> On 7/15/2015 12:18 PM, Thomas Zander via bitcoin-dev wrote:
> > 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?
>
> So users/wallets can know when they should rebroadcast and consider
> increasing the fee.
>
>
> Using 12 blocks, there is a 5% chance he has to wait 3 hours.*
>
> Using 120 minutes, there is only a .23% chance that fewer than 4 blocks
> have occurred.**
Using the good old saying; results in the past are no indication of the
future.
I see a logic error in your thinking.
Your assumption that time is a better indicator is false. Naturally time
itself is universal, but blocks are known by wallets too. Its just as good.
This assumption of yours leans heavily on block mining times, and that is
not guaranteed in the future. Imagine one day half the miners dropping and
blocks take much longer for a week or so. Your assumptions just broke the
mempool.
--
Thomas Zander
next prev parent reply other threads:[~2015-07-16 9:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-15 0:24 Tom Harding
2015-07-15 19:18 ` Thomas Zander
2015-07-15 23:15 ` Tom Harding
2015-07-16 9:38 ` Thomas Zander [this message]
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=2509294.8eWsy7oNj2@coldstorage \
--to=thomas@thomaszander$(echo .)se \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/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