From: ZmnSCPxj <ZmnSCPxj@protonmail•com>
To: ZmnSCPxj <ZmnSCPxj@protonmail•com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Block solving slowdown
Date: Tue, 31 Mar 2020 02:06:32 +0000 [thread overview]
Message-ID: <3jzOExUBfhtM7U4lx3jMHsyHjx0Jb59CPNFso3I4zyT7S8JPRZ5-8PwlZ2Kax998mVj8xwPUB0Prdo7f0tvZnhru7xKofpsYtGJBHlmr9wQ=@protonmail.com> (raw)
In-Reply-To: <dUt3gYGhyaMYXiz6ZoS0whlq57ImbjYO8-z4lw4uZkqzMUHjmPoLtRSuQnM3h26wTpVFUsZWM9wH2yGWRPd-bEx2HhvWYuxKRTXYojw5hT4=@protonmail.com>
Good morning Andrew,
Another thing I did not consider is how miners will actually behave under this ruleset.
Miners are the direct beneficiaries of any increased inflation rate voted in.
Miners are also ultimately the ones who decide which transactions get added into blocks, or put another way, which UTXOs are deleted and which UTXOs are created.
Thus, miners are likely to accept attempts to delete UTXOs that vote for lower inflation rates and create UTXOs that vote for higher inflation rates, and reject attempts to delete UTXOs that vote for higher inflation rates and create UTXOs that vote for lower inflation rates.
Thus, miners will end up strongly controlling the inflation rate of the coin.
Even worse, since the inflation gives increased coins to miners, more and more of the value of the coin, with which you vote for, will be in the hands of miners, who can then vote directly instead of censoring votes they dislike.
The entire point of Bitcoin having a fixed inflation rate schedule (that is ultimately disinflationary) is to avoid the moral hazard of having the beneficiaries of higher inflation rates also be the ones who decide what the inflation rate will be.
Regards,
ZmnSCPxj
prev parent reply other threads:[~2020-03-31 2:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-21 18:40 [bitcoin-dev] Block solving slowdown question/poll Dave Scotese
2020-03-22 7:54 ` David A. Harding
2020-03-22 11:58 ` LORD HIS EXCELLENCY JAMES HRMH
2020-03-22 16:54 ` Eric Voskuil
2020-03-22 18:17 ` Dave Scotese
2020-03-23 12:59 ` Andrew Cann
2020-03-23 18:39 ` Dave Scotese
2020-03-24 7:42 ` ZmnSCPxj
2020-03-25 15:23 ` Andrew Cann
2020-03-26 1:42 ` ZmnSCPxj
2020-03-27 9:17 ` Andrew Cann
2020-03-28 2:12 ` ZmnSCPxj
2020-03-29 8:11 ` [bitcoin-dev] Block solving slowdown Andrew Cann
2020-03-30 2:59 ` ZmnSCPxj
2020-03-31 2:06 ` ZmnSCPxj [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='3jzOExUBfhtM7U4lx3jMHsyHjx0Jb59CPNFso3I4zyT7S8JPRZ5-8PwlZ2Kax998mVj8xwPUB0Prdo7f0tvZnhru7xKofpsYtGJBHlmr9wQ=@protonmail.com' \
--to=zmnscpxj@protonmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.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