From: "Jeremy Spilman" <jeremy@taplink•co>
To: "Andreas Petersson" <andreas@petersson•at>,
"Peter Todd" <pete@petertodd•org>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Making fee estimation better
Date: Fri, 25 Oct 2013 12:35:34 -0700 [thread overview]
Message-ID: <op.w5izdkiyyldrnw@laptop-air> (raw)
In-Reply-To: <20131025161323.GA15774@petertodd.org>
Do you think we're at the point where wallets have to be able to "actively
bid" the fee using replacement due to block contention?
I think a fee estimation API is just a data point. Depending on the
properties of the estimator, and how that's presented in the UI, it could
serve to either increase or decrease the need for recovery.
Like you said, we already have "fee estimation" in the form of "user,
please estimate the fee!" Now we want to make fee estimation "better", and
one key aspect of better fee estimation is decreasing the need for
recovery. Techniques like signing multiple transactions with different fee
levels should become less useful the better you are at estimating the fee.
What I find interesting is that fee estimation can look at the size and
type of the transaction, the age of the inputs, the number of inputs
versus outputs, amount of the outputs, factor in [assumptions about] what
fee policies miners are actually using, and after all that, look at the
actual competing transactions on the blockchain and try to figure out how
many of those are even real.
For example, if you just look at fee-per-KB of mempool versus fee-per-KB
of recently mined transactions, without taking into account input age,
number of inputs vs outputs, output amounts... all the other things miner
might have used to discriminate between transactions, then I don't think
you'll end up with a better fee estimator.
Contention might bump you out of a few blocks, but if the basis for
calculating the fee is fundamentally compatible with the relay policies
and the transaction-inclusion policies being run by large mining pools,
the transaction isn't dead, it's just pending.
On Fri, 25 Oct 2013 09:13:23 -0700, Peter Todd <pete@petertodd•org> wrote:
> On Fri, Oct 25, 2013 at 02:02:35PM +0200, Andreas Petersson wrote:
>>
>>
>> > Worth thinking about the whole ecosystem of wallets involved; they all
>> > have to handle double-spends gracefully to make tx replacement of any
>> > kind user friendly. We should try to give people a heads up that this
>> is
>> > coming soon if that's your thinking.
>>
>> If there is a situation where wallets are supposed to constantly monitor
>> the tx propagation and recreate their transactions with different fees,
>> this would make a lot of usecases inconvenient.
>> half-offline bluetooth transactions, users with unstable connections,
>> battery power lost, etc, etc. - and last but not least power concerns on
>> hardware wallets on the bitcoincard (tx signing drains a significant
>> amount
>> of power and should therefore only be done once)
>
> Anyway, as I've said repeatedly my problem with fee estimation is that
> it needs to be combined with some form of transaction replacement to
> give users a way to recover from bad estimates, not that I think the
> idea shouldn't be implemented at all. After all, we alrady have fee
> estimation: wallet authors and users manully estimate fees!
>
> This particular case is a nasty one re: recovering from a bad estimate,
> and it's exactly why the payment protocol is designed for the sender to
> give the receiver a copy of every transaction they make so the receiver
> can be held responsible for getting them mined, eg. with
> child-pays-for-parent, out-of-band fee payment, or maybe even by adding
> inputs to the transaction. (SIGHASH_ANYONECANPAY)
next prev parent reply other threads:[~2013-10-25 19:35 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-24 14:30 Peter Todd
2013-10-24 14:38 ` Mike Hearn
2013-10-24 14:43 ` Peter Todd
2013-10-24 14:46 ` Mike Hearn
2013-10-24 14:54 ` Peter Todd
2013-10-24 20:39 ` Gavin Andresen
2013-10-25 7:07 ` Peter Todd
2013-10-25 12:02 ` Andreas Petersson
2013-10-25 13:29 ` Mark Friedenbach
2013-10-25 14:08 ` Andreas Petersson
2013-10-25 16:13 ` Peter Todd
2013-10-25 19:35 ` Jeremy Spilman [this message]
2013-10-25 22:13 ` Peter Todd
2013-10-25 7:51 ` Jeremy Spilman
2013-10-25 22:49 ` Peter Todd
2013-10-26 0:25 ` Gavin Andresen
2013-10-26 7:28 ` Peter Todd
2013-10-28 7:17 ` John Dillon
2013-11-04 10:52 ` [Bitcoin-development] Zeroconf-safe tx replacement (replace-for-fee) Peter Todd
2013-11-04 11:10 ` Adam Back
2013-11-04 11:59 ` Peter Todd
[not found] <mailman.289181.1382717617.21953.bitcoin-development@lists.sourceforge.net>
2013-10-25 16:40 ` [Bitcoin-development] Making fee estimation better Tamas Blummer
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=op.w5izdkiyyldrnw@laptop-air \
--to=jeremy@taplink$(echo .)co \
--cc=andreas@petersson$(echo .)at \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=pete@petertodd$(echo .)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