To: Gregory Maxwell <greg@xiph.org>
References: <CAPzrG5bFTbRERHQsmyFeZwiuakgSW5UCC8EtYfAm4j9EDtcLeg@mail.gmail.com>
	<CAGCathyVqQcBCKORQebicWq+OQfKZVLXb0g_9QHBu2e-jqYBgg@mail.gmail.com>
	<CAC94VgAoZFwu4TC8CdNP9cbxUiFgQP4bOsXykJyb4+8y-eSY1Q@mail.gmail.com>
	<261a9388-64fe-a664-85f0-4b0e8ca9ec1e@voskuil.org>
	<CAAS2fgQcMr231G4hF0rdp0M-rxOzLm07VHEdUuQ2BMnLa3A26g@mail.gmail.com>
	<7ecea1c8-bc60-223e-6e7b-48b390363794@voskuil.org>
	<CAAS2fgRcaRF5-8k94rL+fOjK2RJf0cjj+uqD+-db_VNZu9t8Xw@mail.gmail.com>
From: Eric Voskuil <eric@voskuil.org>
Message-ID: <d920046d-fee5-0f05-068a-87441e332382@voskuil.org>
Date: Mon, 29 Jan 2018 19:52:21 -0800
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
	Thunderbird/52.5.2
MIME-Version: 1.0
In-Reply-To: <CAAS2fgRcaRF5-8k94rL+fOjK2RJf0cjj+uqD+-db_VNZu9t8Xw@mail.gmail.com>
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="Aix30T8XGWYCbC3nTh9i9SLpRu5NoYGKb"
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Proposal: rewarding fees to next block miner
Precedence: list

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--Aix30T8XGWYCbC3nTh9i9SLpRu5NoYGKb
Content-Type: multipart/mixed; boundary="89pUml0FhomYRtu2Gx3K2XE2NBmg51IKO";
 protected-headers="v1"
From: Eric Voskuil <eric@voskuil.org>
To: Gregory Maxwell <greg@xiph.org>
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>,
 George Balch <gbalch714@gmail.com>, Lucas Clemente Vella <lvella@gmail.com>
Message-ID: <d920046d-fee5-0f05-068a-87441e332382@voskuil.org>
Subject: Re: [bitcoin-dev] Proposal: rewarding fees to next block miner
References: <CAPzrG5bFTbRERHQsmyFeZwiuakgSW5UCC8EtYfAm4j9EDtcLeg@mail.gmail.com>
 <CAGCathyVqQcBCKORQebicWq+OQfKZVLXb0g_9QHBu2e-jqYBgg@mail.gmail.com>
 <CAC94VgAoZFwu4TC8CdNP9cbxUiFgQP4bOsXykJyb4+8y-eSY1Q@mail.gmail.com>
 <261a9388-64fe-a664-85f0-4b0e8ca9ec1e@voskuil.org>
 <CAAS2fgQcMr231G4hF0rdp0M-rxOzLm07VHEdUuQ2BMnLa3A26g@mail.gmail.com>
 <7ecea1c8-bc60-223e-6e7b-48b390363794@voskuil.org>
 <CAAS2fgRcaRF5-8k94rL+fOjK2RJf0cjj+uqD+-db_VNZu9t8Xw@mail.gmail.com>
In-Reply-To: <CAAS2fgRcaRF5-8k94rL+fOjK2RJf0cjj+uqD+-db_VNZu9t8Xw@mail.gmail.com>

--89pUml0FhomYRtu2Gx3K2XE2NBmg51IKO
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable

On 01/29/2018 05:59 PM, Gregory Maxwell wrote:
> 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.
>=20
> 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.

The miner who creates a block owns the block, he/she has selected the
transactions and directs the reward. The case for this could hardly be
stronger.

The fact that there is subsidy implies that *part* of the cost of
creating the block is offset. But by not accepting the highest fee
transactions the miner is still accepting a net loss by purchasing the
space for himself. The hash power generated by the miner to create the
block contributes to confirmation security to a greater degree than for
which he has been rewarded.

You seem to be implying that there is dishonesty involved in purchasing
block space, or that it is somehow possible to earn reward while not
complying with the protocol. There is no honest or dishonest compliance
with a protocol, there is just compliance or non-compliance.

> 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.

Everyone can do whatever they want with their own machines, and I
haven't argued otherwise. As far as "rights" go, Bitcoin doesn't care.
I'm not one who has regularly raised hard fork fears while at the same
time threatening them. My objective is to dispel flawed reasoning, not
to negotiate for the rights of some group over another.

Some economic theories that get thrown around are baffling, this idea of
"retaliation" among them. Presumably the objective is to reduce
transaction confirmation costs. The theory would be that mining empty
blocks or mining own transactions is "unfairly" increasing revenue to
miners. Despite the incorrectness of this theory, the proposed cure
attempts to reduce returns to miners. However the consequence of
reducing returns to miners is simply a reduction of hash power (as the
least efficient miners become insolvent). Miners will continue to earn
the same rate of return on their capital as always. And the cost of
transactions will remain the same...

The presumed mechanism of the proposed retaliation is also baffling. A
miner (or anyone) can always create transactions, pay fees, and send
them out to the network. Given that we presume transactions without
identity, it is not possible (or desirable) to detect the source of
transactions. Maybe the assumption is that sending such transactions out
to the network would not satisfy the miner's objective, since the fees
cannot be "recovered". But this is the original flaw. Fees spent to
one's self cannot be recovered either! So if a miner wants to blow money
by filling up blocks with market fee transactions, they will be able to
do so at the same cost no matter how one tries to "retaliate".

e


--89pUml0FhomYRtu2Gx3K2XE2NBmg51IKO--

--Aix30T8XGWYCbC3nTh9i9SLpRu5NoYGKb
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iQEcBAEBAgAGBQJab+v1AAoJEDzYwH8LXOFOEJYH/1vQJpqkj6jtvD6WSjifC8wq
sTOuwbsCE3KCHQoVIlt68SKd1mVt5BFTxVftmqrWqMDACaq/ovEzan+o1S4MCMQX
8FL926rkqees6wHInEcVSiIyHQ/Oh9Dyh91RTqkdghfJWNPTfpoIieOZpCK7nweD
Rmad55YnZfC3xrTQ7AddmJmpE4cefTseGNNL9JAL4xlFV0AYJhLLetKWnOp3GnVK
wSVgAKNe39WNNmiu1sG8pwCZa73oXAnujGPsWNYhtfsgOH/PWnZ2kevt30XuJj1/
3WCgdM8QukA8zHkKt0ljU+Mfp06sfFfcidCZR9hT49Y3kxA0muK7w7ZwY590Zmo=
=TXsr
-----END PGP SIGNATURE-----

--Aix30T8XGWYCbC3nTh9i9SLpRu5NoYGKb--