public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Tamas Blummer <tamas@bitsofproof.com>
To: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Making fee estimation better
Date: Fri, 25 Oct 2013 18:40:08 +0200	[thread overview]
Message-ID: <C3388417-98E9-4C80-8E26-05DD9BB6E9C2@bitsofproof.com> (raw)
In-Reply-To: <mailman.289181.1382717617.21953.bitcoin-development@lists.sourceforge.net>

Two thoughts:
1. Please keep it simple, miner will override it either.
2. If block construction algorithm compares alternate chains and not individual transactions,  then receiver can bump up the fee by spending the unconfirmed output again with higher fee, no need for replacement in the mempool.

Tamas Blummer




       reply	other threads:[~2013-10-25 16:59 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.289181.1382717617.21953.bitcoin-development@lists.sourceforge.net>
2013-10-25 16:40 ` Tamas Blummer [this message]
2013-10-24 14:30 [Bitcoin-development] Making fee estimation better 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
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

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=C3388417-98E9-4C80-8E26-05DD9BB6E9C2@bitsofproof.com \
    --to=tamas@bitsofproof.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    /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