From: Eric Voskuil <eric@voskuil•org>
To: Gregory Maxwell <greg@xiph•org>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Proposal: rewarding fees to next block miner
Date: Mon, 29 Jan 2018 15:21:48 -0800 [thread overview]
Message-ID: <7ecea1c8-bc60-223e-6e7b-48b390363794@voskuil.org> (raw)
In-Reply-To: <CAAS2fgQcMr231G4hF0rdp0M-rxOzLm07VHEdUuQ2BMnLa3A26g@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1572 bytes --]
On 01/29/2018 01:22 PM, Gregory Maxwell wrote:
> On Mon, Jan 29, 2018 at 4:49 AM, Eric Voskuil via bitcoin-dev
> <bitcoin-dev@lists•linuxfoundation.org> wrote:
>> I'm not sure who cooked up this myth about miners gaining advantage over
>> those who buy block space by mining empty space, rejecting higher-fee
>> transactions, and/or mining "recovery" transactions, but the idea is
>> complete nonsense.
>
> I agree.
>
> Steel-manning it, I guess I could argue that empty blocks are slightly
> more conspicuous and might invite retaliation especially given the
> high levels of mining centralization creates retaliation exposure. ...
> but dummy transactions are hardly less conspicuous, many nodes log now
> when blocks show up containing txn that they've never seen before.
> Moreover, inexplicably underfilled blocks are produced (e.g. by
> bitmain's antpool) and no retaliation seems to be forthcoming.
It's not clear to me what would be the reason for retaliation, given
there is no more harm in a miner purchasing a block than Coinbase
submitting enough transactions to fill a block. Both pay the market rate
for the space. But since the former results in a loss, a financial
consequence ("retaliation") is inherent.
If a farmer destroys his/her own apple crop he loses money. It may be
very conspicuous, but nobody would retaliate as only the farmer's own
property was affected. Customers would just get their apples elsewhere.
Block space created by a miner is property that belongs to the miner, it
can be sold or not sold.
e
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2018-01-29 23:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-27 8:45 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 [this message]
2018-01-30 1:59 ` Gregory Maxwell
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=7ecea1c8-bc60-223e-6e7b-48b390363794@voskuil.org \
--to=eric@voskuil$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=greg@xiph$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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