public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Mike Hearn <mike@plan99.net>
To: Peter Todd <pete@petertodd.org>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Making fee estimation better
Date: Thu, 24 Oct 2013 16:38:16 +0200	[thread overview]
Message-ID: <CANEZrP100Lg_1LcFMKx1yWrGTSFb5GZmLmXNbZjPGaiEgOeuwA@mail.gmail.com> (raw)
In-Reply-To: <20131024143043.GA12658@savin>

[-- Attachment #1: Type: text/plain, Size: 788 bytes --]

On Thu, Oct 24, 2013 at 4:30 PM, Peter Todd <pete@petertodd.org> wrote:

> Quick thought on how to make blockchain-based fee estimates work better
> in the context of out-of-band mining contracts: have miners advertise in
> their coinbase's what fees were actually paid, as opposed to appear to
> have been paid.


This is interesting, but I suppose some miners may have business models
that can't be easily summed up as a "fee" - like all-you-can-eat deals with
certain providers, or preference to certain kinds of transactions etc.

For the concern that estimation might force fees down too far if miners
include private transactions, I thought the estimates were calculated only
on broadcast transactions, so transactions that just appear in a block
won't ever influence the estimate?

[-- Attachment #2: Type: text/html, Size: 1158 bytes --]

  reply	other threads:[~2013-10-24 14:38 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-24 14:30 [Bitcoin-development] Making fee estimation better Peter Todd
2013-10-24 14:38 ` Mike Hearn [this message]
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
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=CANEZrP100Lg_1LcFMKx1yWrGTSFb5GZmLmXNbZjPGaiEgOeuwA@mail.gmail.com \
    --to=mike@plan99.net \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=pete@petertodd.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