From: Eric Voskuil <eric@voskuil•org>
To: Andrew <onelineproof@gmail•com>
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Selfish Mining Prevention
Date: Mon, 17 Sep 2018 12:36:15 -0700 [thread overview]
Message-ID: <49CC1792-9397-4506-B2FC-F3B6C14EA355@voskuil.org> (raw)
In-Reply-To: <CAL8tG=mXXtT-W5zW6H25jNY_H8cr+2JK66ocpjptw+T3W+VwYQ@mail.gmail.com>
> Once hashrate gets large enough, no new miners (additional
hashrate) will want to join since their share of the hashrate is too
small to make a profit.
The share (hash power) of a miner is proportional to capital investment, not the newness of that investment. The efficiency of a new mine (inclusive of pooling pressures) can certainly be sufficient to outperform other miners, resulting in the departure of the latter, thus not preventing the entry of the former.
The point you should be making here is that energy consumption is regulated by the cost of capital (in addition to reward value and the cost of energy).
Note that higher efficiency mining does not reduce energy consumption, nor does variation in the necessary cost of mining hardware. The total energy cost is the control, not the hash rate. This is of course why proof-of-memory (space) is pointless. It simply shifts most of the energy cost to hardware manufacture, shipment, etc.
e
On Sep 17, 2018, at 06:18, Andrew <onelineproof@gmail•com> wrote:
>> I see what you say, however, since the proposal as I have read it says "And this will keep happening as long as hashrate keeps rising," - what actually happens in the case hashrate stagnates or falls?
>
> In general, a target hashrate can be set by users (can be less or more
> than the peak hashrate). As long as hashrate is rising and still
> didn't reach the target, miners will incrementally get the reserve
> fees. Once the "contract" times out, the remaining part can be used as
> fees by the users who created the reserve fee "contract". So if
> hashrate remains the same or falls, then users get the reserve fees
> back.
>
> I agree that we can't stop people from being greedy. If they are not
> Bitcoin mining, they will try to put their energy to earn in some
> other way...The hashrate is related the demand for Bitcoin (price) and
> the amount of fees/subsidies the miners will get paid. For every level
> of mining rewards (based on demand) there exists a limit on the
> hashrate. Once hashrate gets large enough, no new miners (additional
> hashrate) will want to join since their share of the hashrate is too
> small to make a profit.
>
> Also with merge mining and proof of space we can be quite efficient in
> the future. But of course I sympathize with the "don't be greedy"
> philosophy, and it can be good to educate people to use less resources
> than they need, just I think it's a bit outside of the scope of what
> the Bitcoin software protocol does.
next prev parent reply other threads:[~2018-09-17 19:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-01 0:11 Andrew
2018-09-13 23:19 ` Andrew
2018-09-14 14:49 ` Moral Agent
2018-09-14 17:30 ` Andrew
2018-09-14 18:00 ` Moral Agent
2018-09-15 5:29 ` Damian Williamson
2018-09-15 16:01 ` Andrew
2018-09-15 22:45 ` Damian Williamson
2018-09-16 23:20 ` Eric Voskuil
2018-09-17 13:18 ` Andrew
2018-09-17 15:40 ` Eric Voskuil
2018-09-17 19:36 ` Eric Voskuil [this message]
2018-09-17 14:09 Zawy
2018-09-18 20:26 ` Andrew
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=49CC1792-9397-4506-B2FC-F3B6C14EA355@voskuil.org \
--to=eric@voskuil$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=onelineproof@gmail$(echo .)com \
/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