From: Martin Lie <martin@datamagi•no>
To: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Proposal: SPV Fee Discovery mechanism
Date: Thu, 11 Jun 2015 16:11:51 +0200 [thread overview]
Message-ID: <55799727.7090902@datamagi.no> (raw)
In-Reply-To: <20150611131048.GA24053@savin.petertodd.org>
Peter Todd wrote:
> Re: "dropped in an unpredictable way" - transactions would be dropped
> lowest fee/KB first, a completely predictable way.
It would be 'completely predictable' for whoever knew the state and
policies of a miner's mempool, but from an end user's perspective that
wouldn't matter much: The end users wouldn't know if their
transaction(s) would make the cut or not, somewhere in the network, and
by what time. They (obviously) won't know what miners will find the next
block(s), they won't know the miners' mempool sizes, potential custom
eviction policies, etc.
I agree that this can be somewhat remedied by FSSRBF/CPFP, though,
provided wallets give users a good (semi-automated?) interface for such
transaction replacements/chains.
--
Martin Lie
next prev parent reply other threads:[~2015-06-11 14:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-10 17:37 Nathan Wilcox
2015-06-10 19:19 ` Aaron Voisine
2015-06-10 20:00 ` Nathan Wilcox
2015-06-10 20:03 ` Peter Todd
2015-06-11 18:30 ` Nathan Wilcox
2015-06-11 18:55 ` Aaron Voisine
2015-06-13 15:38 ` Nathan Wilcox
2015-06-10 21:18 ` Aaron Voisine
2015-06-10 20:26 ` Mike Hearn
2015-06-10 21:18 ` Aaron Voisine
2015-06-11 10:19 ` Mike Hearn
2015-06-11 13:10 ` Peter Todd
2015-06-11 14:11 ` Martin Lie [this message]
2015-06-11 17:10 ` Tom Harding
2015-06-11 17:52 ` Mike Hearn
2015-06-12 6:44 ` Aaron Voisine
2015-06-11 18:18 ` Nathan Wilcox
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=55799727.7090902@datamagi.no \
--to=martin@datamagi$(echo .)no \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/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