public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Gregory Maxwell <greg@xiph.org>
To: Eric Voskuil <eric@voskuil.org>
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Proposal: rewarding fees to next block miner
Date: Tue, 30 Jan 2018 01:59:48 +0000	[thread overview]
Message-ID: <CAAS2fgRcaRF5-8k94rL+fOjK2RJf0cjj+uqD+-db_VNZu9t8Xw@mail.gmail.com> (raw)
In-Reply-To: <7ecea1c8-bc60-223e-6e7b-48b390363794@voskuil.org>

On Mon, Jan 29, 2018 at 11:21 PM, Eric Voskuil <eric@voskuil.org> wrote:
> Block space created by a miner is property that belongs to the miner, it
> can be sold or not sold.

That case would be stronger when there is no more subsidy, but we
collectively the uses of Bitcoin are currently paying miners around
$130k USD per block in the form of inflation for the job of honestly
complying with the Bitcoin protocol.

I don't think you can argue that they have any more right to do that
than any of us have a right to run software that invalidates their
coinbase outputs when they do; which would be the sort of retaliation
they might get targeted with.


  reply	other threads:[~2018-01-30  1:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-27  8:45 [bitcoin-dev] Proposal: rewarding fees to next block miner Nathan Parker
2018-01-27 19:06 ` Gregory Maxwell
2018-01-27 23:48   ` Eric Voskuil
2018-01-28 16:54 ` Lucas Clemente Vella
2018-01-29  0:46   ` Eric Voskuil
2018-01-29  1:44   ` George Balch
2018-01-29  4:49     ` Eric Voskuil
2018-01-29 21:22       ` Gregory Maxwell
2018-01-29 23:21         ` Eric Voskuil
2018-01-30  1:59           ` Gregory Maxwell [this message]
2018-01-30  3:52             ` Eric Voskuil

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=CAAS2fgRcaRF5-8k94rL+fOjK2RJf0cjj+uqD+-db_VNZu9t8Xw@mail.gmail.com \
    --to=greg@xiph.org \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=eric@voskuil.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