1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
|
Return-Path: <eric@voskuil.org>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 49BB9E25
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 17 Sep 2018 19:36:20 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-pl1-f194.google.com (mail-pl1-f194.google.com
[209.85.214.194])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 4A0C142D
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 17 Sep 2018 19:36:19 +0000 (UTC)
Received: by mail-pl1-f194.google.com with SMTP id u11-v6so7896207plq.5
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 17 Sep 2018 12:36:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=voskuil-org.20150623.gappssmtp.com; s=20150623;
h=mime-version:subject:from:in-reply-to:date:cc
:content-transfer-encoding:message-id:references:to;
bh=Nrv1L6y9kwOdRdQc6e3YqF4CGEnEa7JcqmIQ58umFAs=;
b=OR+04l8QU3O8Rrk2nUDgtTUIYw8ccKTG1MhWloV16HH31rvBZT2XlbQ1OXe9rmZiHE
IecM9ZEiSkxcE9MAS/pN4zvc4x9Nznaa4i4Q0j+DKUoKbn0tLmKZKOQgA3ulf/ogXEIR
owBotuE50TBkCWsm4VHQBu3tPD7vMmnWrv4voVCbz+Y+39hcjUn5kOQ1YxYj8iGs3cJo
7kkBbwjRLM2WGxUwJfb+dVV5sVKayaBCHvQT6WEpM4USfZwjFShXx1xOocQJYfLfJrTk
CTDJFYIdOp1THK1jtJhcdDQtRQgg9e18IaJqnXbQspNJ/pCOxBYuJ5qXMlhAPshm7s4F
/NMQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc
:content-transfer-encoding:message-id:references:to;
bh=Nrv1L6y9kwOdRdQc6e3YqF4CGEnEa7JcqmIQ58umFAs=;
b=AcNapmS9vKhOSzzwG48UP/6PVx6k1GgJbNYC+17lI6amtB3SnqSUHUF+CKhH3EROKR
uhAWAfOIQnxsZ7EN3l3OhfXrxPURDheb4kJsXDx9T7aXgP9K1FIwE1rCdQeg8aL0hYp6
O11Wdy8dci+jTbAMhxPGkxPNb2/S+xlFs82qseCum2NFrmtyGaV633qQF953vTwnL1dt
DfufWKDhck4gM5DKzwYwpkfXPZBNJ/yRtjnpaGJG3qTIeM5ZpcexuyBeTKy0JSkq7VB6
oH3R80wpq0jxRh+geN5v8JJGmGSyVJKEXKSI4frM4Y6nJYwWIQ67/BIAAEalfwL9QbDz
R3rQ==
X-Gm-Message-State: APzg51BDl5Nh+bFyovd7a5gRulXfLq2B4EvCURgk/H/BuT//KEQqe8+2
1cvpU14lPZVjISNLdmdqtxWp7Q==
X-Google-Smtp-Source: ANB0VdYJaBoSWP0ilfS/NVJrNmKamcx3d0eECQGo7eWvnHUVRbzeyR5yrXlkHNnw3p7adF3YteijYA==
X-Received: by 2002:a17:902:6ac5:: with SMTP id
i5-v6mr26274167plt.232.1537212978722;
Mon, 17 Sep 2018 12:36:18 -0700 (PDT)
Received: from ?IPv6:2600:380:4478:499a:d987:c483:a891:25c4?
([2600:380:4478:499a:d987:c483:a891:25c4])
by smtp.gmail.com with ESMTPSA id
q26-v6sm27513435pfj.127.2018.09.17.12.36.17
(version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
Mon, 17 Sep 2018 12:36:17 -0700 (PDT)
Content-Type: text/plain;
charset=us-ascii
Mime-Version: 1.0 (1.0)
From: Eric Voskuil <eric@voskuil.org>
X-Mailer: iPhone Mail (15G77)
In-Reply-To: <CAL8tG=mXXtT-W5zW6H25jNY_H8cr+2JK66ocpjptw+T3W+VwYQ@mail.gmail.com>
Date: Mon, 17 Sep 2018 12:36:15 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <49CC1792-9397-4506-B2FC-F3B6C14EA355@voskuil.org>
References: <CAL8tG=k+kXHMbQdUXO3BXKv7fQwp5t2QuaQut7sPUtEYgwzn0A@mail.gmail.com>
<CAL8tG=mui_izrob0V66QqNzSJs1Lpbm0xxUYMpzb65-JR9QhRw@mail.gmail.com>
<PS2P216MB017942E0336DD337CB1EB6A89D180@PS2P216MB0179.KORP216.PROD.OUTLOOK.COM>
<CAL8tG==LgUecK5bbZ-FcwSZvJzVuK3nGu6cCUNFMPi4uR0CriA@mail.gmail.com>
<PS2P216MB0179A4E6401D831166E749089D180@PS2P216MB0179.KORP216.PROD.OUTLOOK.COM>
<B1863BA1-59D4-40FD-8D6E-8991BC25BFC8@voskuil.org>
<CAL8tG=mXXtT-W5zW6H25jNY_H8cr+2JK66ocpjptw+T3W+VwYQ@mail.gmail.com>
To: Andrew <onelineproof@gmail.com>
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID, MIME_QP_LONG_LINE,
RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
X-Mailman-Approved-At: Tue, 18 Sep 2018 04:32:16 +0000
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Selfish Mining Prevention
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Sep 2018 19:36:20 -0000
> 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 p=
ooling pressures) can certainly be sufficient to outperform other miners, re=
sulting 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 b=
y 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 d=
oes variation in the necessary cost of mining hardware. The total energy cos=
t 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 ma=
nufacture, 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 "A=
nd this will keep happening as long as hashrate keeps rising," - what actual=
ly happens in the case hashrate stagnates or falls?
>=20
> 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.
>=20
> 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.
>=20
> 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.
|
