From: Bram Cohen <bram@bittorrent.com>
To: praxeology_guy <praxeology_guy@protonmail.com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Refund Excesss Fee Hard Fork Proposal
Date: Fri, 31 Mar 2017 13:57:04 -0700 [thread overview]
Message-ID: <CA+KqGkoSQEE-MzC8ptbFxoypKKFpMMK8XQXdvkgkJghfP7sy4Q@mail.gmail.com> (raw)
In-Reply-To: <1dvInLVM9fq2GjQVacau8gDyslYCCx_6dm2Sbi1IiIyPaXy1C8-Ip3CSICVal_VO_FKzVaQCfRVUImQmKuNuNXfKzqhnwAM1Cw_lyQVL8ew=@protonmail.com>
[-- Attachment #1: Type: text/plain, Size: 896 bytes --]
On Fri, Mar 31, 2017 at 1:29 PM, praxeology_guy via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:
>
> Change the fee policy to cause all fee/byte in a block to be reduced to
> the lowest included fee/byte. Change transactions to specify how/which
> outputs get what portions of [(TX_fee/TX_length - LIFB)*TX_length].
> Transactions of course could still offer the remainder to the miner if they
> don't want to modify some of the outputs and don't want to reveal their
> change output.
>
That would have the unfortunate effect of incentivizing miners to not
completely fill blocks, because low fee marginal transactions could cost
them money.
An alternate approach would be to incentivize miners to follow transaction
fees more by reducing mining rewards, which could be done by soft forking
in a requirement that a chunk of all mining rewards be sent to an
unspendable address.
[-- Attachment #2: Type: text/html, Size: 1298 bytes --]
next prev parent reply other threads:[~2017-03-31 20:57 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 [this message]
2017-03-31 21:17 ` praxeology_guy
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=CA+KqGkoSQEE-MzC8ptbFxoypKKFpMMK8XQXdvkgkJghfP7sy4Q@mail.gmail.com \
--to=bram@bittorrent.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=praxeology_guy@protonmail.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