From: praxeology_guy <praxeology_guy@protonmail.com>
To: Bram Cohen <bram@bittorrent.com>
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Refund Excesss Fee Hard Fork Proposal
Date: Fri, 31 Mar 2017 17:17:16 -0400 [thread overview]
Message-ID: <rrMTVqlEe7A5uHTOaUIuIlQ17uo9BOswBiDDtG_73l3hWbTyWHDxZ-3oSIceyHOddBu83XbQrsEPcTy7A-v75pf6hLeu5pRbO6k7qAuYLS0=@protonmail.com> (raw)
In-Reply-To: <CA+KqGkoSQEE-MzC8ptbFxoypKKFpMMK8XQXdvkgkJghfP7sy4Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 438 bytes --]
> That would have the unfortunate effect of incentivizing miners to not completely fill blocks, because low fee marginal transactions could cost them money.
Look at the fee distribution. The vast majority of fee income comes from txs w/ fees near the LIFB. The blocks will be full... but I guess this would make Child Pays For Parent undesirable. CPFP would need a flag saying it is CPFP so that the parent fee isn't considered the LIFB.
[-- Attachment #2: Type: text/html, Size: 514 bytes --]
prev parent reply other threads:[~2017-03-31 21:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-31 20:29 [bitcoin-dev] Refund Excesss Fee Hard Fork Proposal praxeology_guy
2017-03-31 20:57 ` Bram Cohen
2017-03-31 21:17 ` praxeology_guy [this message]
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='rrMTVqlEe7A5uHTOaUIuIlQ17uo9BOswBiDDtG_73l3hWbTyWHDxZ-3oSIceyHOddBu83XbQrsEPcTy7A-v75pf6hLeu5pRbO6k7qAuYLS0=@protonmail.com' \
--to=praxeology_guy@protonmail.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=bram@bittorrent.com \
/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