summaryrefslogtreecommitdiff
path: root/9a/11ef78b43030572bd85609960b5c0741d15bfd
blob: 5fe4bed721e3155114f0b2308fa712f7a2cffe1d (plain)
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
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
Return-Path: <zachgrw@gmail.com>
Received: from smtp1.osuosl.org (smtp1.osuosl.org [140.211.166.138])
 by lists.linuxfoundation.org (Postfix) with ESMTP id 0D932C0001
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Sun, 16 May 2021 21:15:34 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by smtp1.osuosl.org (Postfix) with ESMTP id E3F0383704
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Sun, 16 May 2021 21:15:33 +0000 (UTC)
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: 0.604
X-Spam-Level: 
X-Spam-Status: No, score=0.604 tagged_above=-999 required=5
 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
 DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001,
 HTML_FONT_FACE_BAD=0.001, HTML_FONT_LOW_CONTRAST=0.001,
 HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001,
 SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: smtp1.osuosl.org (amavisd-new);
 dkim=pass (2048-bit key) header.d=gmail.com
Received: from smtp1.osuosl.org ([127.0.0.1])
 by localhost (smtp1.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id wEBqatxHJS5o
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Sun, 16 May 2021 21:15:32 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.8.0
Received: from mail-il1-x135.google.com (mail-il1-x135.google.com
 [IPv6:2607:f8b0:4864:20::135])
 by smtp1.osuosl.org (Postfix) with ESMTPS id AA55B834AE
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Sun, 16 May 2021 21:15:32 +0000 (UTC)
Received: by mail-il1-x135.google.com with SMTP id h6so4360797ila.7
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Sun, 16 May 2021 14:15:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
 h=mime-version:references:in-reply-to:from:date:message-id:subject:to;
 bh=HIRwTAmxdMWkc3uXDbF2i+9vDzMnNb6TiI9J4UeCCuc=;
 b=M5wjNWcZwy6RewLnvGW+dcl/34apqVjVZLs3oTgd5HyeaaEJDNi+4hwDTqU4lSF7jZ
 KsvBLMG6GIJ53Ql6JV3gjbGgdV8vbU6s4LoZlxiPb/6WLzpQA3o16q7FUxG2B7ZSpo2Y
 mt2N0XagDc7r9/A967JqHD92wZ6VU0NMtBQ3yk9aZOgr3s616cZbORlwWudEdjhrV1os
 ak9HbiBEfqcc5FnQaWadoU3krdaBUaN8ToBUzYqC6ZNXzhhor9Uk2tlVYl8jh/g9/y3/
 hj1YVoQ3gI94VKIzNNq8E7z0KLHTiHCZ0kTNp0AUY3YYqNpH/gItdjex+4IxsW5f3tAw
 ZJoA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20161025;
 h=x-gm-message-state:mime-version:references:in-reply-to:from:date
 :message-id:subject:to;
 bh=HIRwTAmxdMWkc3uXDbF2i+9vDzMnNb6TiI9J4UeCCuc=;
 b=idjoiA/LNpRMWA48b23TVhVT1b2p9BoVGAQDNVv/Pr5/68+agarmzvryM9mmTQjD1F
 i3QYF1HcUB+iUjspSfkDXNLfi+ohocwICem0s94UOsvxWxAhUe7h2CRRN/OG4dji62Y9
 n1CXUv21++HV2okWs0F/bmUKzN+XnBjjblbk5tCfblKGdhe+qsHePtxi42nPKEAdJtI+
 GBi580tNuDwSfanzkbeQH1gDbd8vgSvvNlXUqEl2GqQ+37+ctJhx92qlg1SJNVF0U+dU
 1mBNlj+fVshiq5vXJl7JtSOl3F21Iydk+AwG+Zl1HZJm4aKS0zpRREkUh8j+8pnDoflX
 pbsQ==
X-Gm-Message-State: AOAM5313NTK7wioEC/GO32UCBRTtp2gJdVYAzK9g2/AgDWxa3mXpyUY3
 fGfkt9xokYuA1j9G/Qd2XSA7pdj40IcfowtpPyGSandc
X-Google-Smtp-Source: ABdhPJz1WcKYbTTC/ZsMSAk4FqvAbkfChZ33r4UB71BR5ZjgA3GK4/EFXJj/DWsIYgr1vsxd02zwsqcGbDikLdlO7Bo=
X-Received: by 2002:a92:c5ac:: with SMTP id r12mr3589021ilt.283.1621199731880; 
 Sun, 16 May 2021 14:15:31 -0700 (PDT)
MIME-Version: 1.0
References: <d35dee03-2d19-e80a-c577-2151938f9203@web.de>
 <CALL-=e45Q_spVnFqVvGAK9c3QzZ=-c_WNwCO-y30q7z-j6orSA@mail.gmail.com>
In-Reply-To: <CALL-=e45Q_spVnFqVvGAK9c3QzZ=-c_WNwCO-y30q7z-j6orSA@mail.gmail.com>
From: Zac Greenwood <zachgrw@gmail.com>
Date: Sun, 16 May 2021 23:15:21 +0200
Message-ID: <CAJ4-pEA92=nRn+LoYYnQYURuTyKN8LNJECBXSFr_AEoWP-awNQ@mail.gmail.com>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>,
 Karl <gmkarl@gmail.com>
Content-Type: multipart/alternative; boundary="00000000000020f63e05c278fa4b"
X-Mailman-Approved-At: Sun, 16 May 2021 22:02:36 +0000
Subject: Re: [bitcoin-dev] Proposal: Force to do nothing for first 9 minutes
 to save 90% of mining energy
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.15
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: Sun, 16 May 2021 21:15:34 -0000

--00000000000020f63e05c278fa4b
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

> if energy is only expended for 10% of the same duration, this money must
now be spent on hardware.

More equipment obviously increases the total energy usage.

You correctly point out that the total expenses of a miner are not just
energy but include capital expenses for equipment and operational cost for
staff, rent etc.

Actually, non-energy expenses are perhaps a much larger fraction of the
total cost than you might expect. Miners using excess waste energy such as
Chinese miners close to hydropower stations pay a near zero price for
energy and are unlikely to be bound by the price of electricity.

Unsurprisingly, miners having access to near-free electricity are
responsible for a significant share of the total energy usage of Bitcoin.
Since such energy is often waste energy from renewable sources such as
hydropower, the carbon footprint of Bitcoin is not nearly as alarming as
its energy usage implies. In fact, since mining is a race to the bottom in
terms of cost, these large miners drive out competing miners that employ
more expensive, often non-renewable sources of energy. It=E2=80=99s for ins=
tance
impossible to mine profitably using household-priced electricity. Looking
at it from that angle, access to renewable, near-free waste energy helps
keeping Bitcoin more green than it would otherwise be. To put it another
way: the high energy usage of the Bitcoin network indicates cheap,
otherwise wasted energy is employed.

For your proposal again this means that energy usage would not be likely to
decrease appreciably, because large miners having access to near-free
energy use the block-reward sized budget fully on equipment and other
operational expenses.

On the other hand, roughly every four years the coinbase reward halves,
which does significantly lower the miner budget, at least in terms of BTC.

Zac



On Sun, 16 May 2021 at 21:02, Karl via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:

> [sorry if I haven't replied to the other thread on this, I get swamped
> by email and don't catch them all]
>
> This solution is workable but it seems somewhat difficult to me at this
> time.
>
> The clock might be implementable on a peer network level by requiring
> inclusion of a transaction that was broadcast after a 9 minute delay.
>
> Usually a 50% hashrate attack is needed to reverse a transaction in
> bitcoin.  With this change, this naively appears to become a 5%
> hashrate attack, unless a second source of truth around time and order
> is added, to verify proposed histories with.
>
> A 5% hashrate attack is much harder here, because the users of mining
> pools would be mining only 10% of the time, so compromising mining
> pools would not be as useful.
>
> Historically, hashrate has increased exponentially.  This means that
> the difficulty of performing an attack, whether it is 5% or 50%, is
> still culturally infeasible because it is a multiplicative, rather
> than an exponential, change.
>
> If this approach were to be implemented, it could be important to
> consider how many block confirmations people wait for to trust their
> transaction is on the chain.  A lone powerful miner could
> intentionally fork the chain more easily by a factor of 10.  They
> would need to have hashrate that competes with a major pool to do so.
>
> > How would you prevent miners to already compute the simpler difficulty
> problem directly after the block was found and publish their solution
> directly after minute 9? We would always have many people with a finished=
 /
> competing solution.
>
> Such a chain would have to wait a longer time to add further blocks
> and would permanently be shorter.
>
> > Your proposal won=E2=80=99t save any energy because it does nothing to =
decrease
> the budget available to mine a block (being the block reward).
>
> You are assuming this budget is directly related to energy
> expenditure, but if energy is only expended for 10% of the same
> duration, this money must now be spent on hardware.  The supply of
> bitcoin hardware is limited.
>
> In the long term, it won't be, so a 10% decrease is a stop-gap
> measure.  Additionally, in the long term, we will have quantum
> computers and AI-designed cryptography algorithms, so things will be
> different in a lot of other ways too.
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>

--00000000000020f63e05c278fa4b
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div style=3D"background-color:rgba(0,0,0,0)!important;border-color:rgb(255=
,255,255)!important;color:rgb(255,255,255)!important" dir=3D"auto"><span st=
yle=3D"border-color:rgb(0,0,0) rgb(0,0,0) rgb(0,0,0) rgb(204,204,204);color=
:rgb(0,0,0)">&gt; </span><span style=3D"border-color:rgb(0,0,0) rgb(0,0,0) =
rgb(0,0,0) rgb(204,204,204);color:rgb(0,0,0)">if energy is only expended fo=
r 10% of the same</span><span style=3D"border-color:rgb(255,255,255) rgb(25=
5,255,255) rgb(255,255,255) rgb(74,77,80)!important;color:rgb(255,255,255)!=
important;background-color:rgba(0,0,0,0)!important"><font face=3D"-apple-sy=
stem, HelveticaNeue" style=3D"color:rgb(0,0,0)">=C2=A0</font></span><span s=
tyle=3D"border-color:rgb(0,0,0) rgb(0,0,0) rgb(0,0,0) rgb(204,204,204);colo=
r:rgb(0,0,0)">duration, this money must now be spent on hardware.</span></d=
iv><div style=3D"background-color:rgba(0,0,0,0);border-color:rgb(255,255,25=
5)" dir=3D"auto"><span style=3D"border-color:rgb(0,0,0) rgb(0,0,0) rgb(0,0,=
0) rgb(204,204,204);color:rgb(0,0,0)"><br></span></div><div style=3D"backgr=
ound-color:rgba(0,0,0,0);border-color:rgb(255,255,255)" dir=3D"auto"><span =
style=3D"border-color:rgb(0,0,0) rgb(0,0,0) rgb(0,0,0) rgb(204,204,204);col=
or:rgb(0,0,0)">More equipment obviously increases the total energy usage.</=
span></div><div style=3D"background-color:rgba(0,0,0,0);border-color:rgb(25=
5,255,255)" dir=3D"auto"><span style=3D"border-color:rgb(0,0,0) rgb(0,0,0) =
rgb(0,0,0) rgb(204,204,204);color:rgb(0,0,0)"><br></span></div><div style=
=3D"background-color:rgba(0,0,0,0);border-color:rgb(255,255,255)" dir=3D"au=
to"><span style=3D"border-color:rgb(0,0,0) rgb(0,0,0) rgb(0,0,0) rgb(204,20=
4,204);color:rgb(0,0,0)">You correctly point out that the total expenses of=
 a miner are not just energy but include capital expenses for equipment and=
 operational cost for staff, rent etc.</span></div><div style=3D"background=
-color:rgba(0,0,0,0);border-color:rgb(255,255,255)" dir=3D"auto"><span styl=
e=3D"border-color:rgb(0,0,0) rgb(0,0,0) rgb(0,0,0) rgb(204,204,204);color:r=
gb(0,0,0)"><br></span></div><div style=3D"background-color:rgba(0,0,0,0);bo=
rder-color:rgb(255,255,255)" dir=3D"auto"><span style=3D"border-color:rgb(0=
,0,0) rgb(0,0,0) rgb(0,0,0) rgb(204,204,204);color:rgb(0,0,0)">Actually, no=
n-energy expenses are perhaps a much larger fraction of the total cost than=
 you might expect. Miners using excess waste energy such as Chinese miners =
close to hydropower stations pay a near zero price for energy and are unlik=
ely to be bound by the price of electricity.</span></div><div style=3D"back=
ground-color:rgba(0,0,0,0);border-color:rgb(255,255,255)" dir=3D"auto"><spa=
n style=3D"border-color:rgb(0,0,0) rgb(0,0,0) rgb(0,0,0) rgb(204,204,204);c=
olor:rgb(0,0,0)"><br></span></div><div style=3D"background-color:rgba(0,0,0=
,0)!important;border-color:rgb(32,33,36)!important;color:rgb(255,255,255)!i=
mportant" dir=3D"auto"><span style=3D"border-color:rgb(0,0,0) rgb(0,0,0) rg=
b(0,0,0) rgb(204,204,204);color:rgb(0,0,0)">Unsurprisingly, miners having a=
ccess to near-free electricity are responsible for a significant share of t=
he total energy usage of Bitcoin. Since such energy is often waste energy f=
rom renewable sources such as hydropower, the carbon footprint of Bitcoin i=
s not nearly as alarming as its energy usage implies.</span><span style=3D"=
background-color:rgba(0,0,0,0)!important;border-color:rgb(255,255,255) rgb(=
255,255,255) rgb(255,255,255) rgb(74,77,80)!important;color:rgb(255,255,255=
)!important"><font style=3D"background-color:rgba(0,0,0,0);border-color:rgb=
(255,255,255);color:rgb(0,0,0)">=C2=A0In fact, since mining is a race to th=
e bottom in terms of cost, these large miners drive out competing miners th=
at employ more expensive, often non-renewable sources of energy. It=E2=80=
=99s for instance impossible to mine profitably using household-priced elec=
tricity. Looking at it from that angle, access to renewable, near-free wast=
e energy helps keeping Bitcoin more green than it would otherwise be. To pu=
t it another way: the high energy usage of the Bitcoin network indicates ch=
eap, otherwise wasted energy is employed.</font></span></div><div style=3D"=
background-color:rgba(0,0,0,0);border-color:rgb(32,33,36)" dir=3D"auto"><sp=
an style=3D"background-color:rgba(0,0,0,0);border-color:rgb(255,255,255) rg=
b(255,255,255) rgb(255,255,255) rgb(74,77,80);color:rgb(255,255,255)"><font=
 style=3D"background-color:rgba(0,0,0,0);border-color:rgb(255,255,255);colo=
r:rgb(0,0,0)"><br></font></span></div><div style=3D"background-color:rgba(0=
,0,0,0)!important;border-color:rgb(32,33,36)!important;color:rgb(255,255,25=
5)!important" dir=3D"auto"><font style=3D"border-color:rgb(0,0,0) rgb(0,0,0=
) rgb(0,0,0) rgb(204,204,204);color:rgb(0,0,0)">For your proposal again thi=
s means that energy usage would not be likely to decrease appreciably, beca=
use large miners having access to near-free energy use the block-reward siz=
ed budget fully on equipment and other operational expenses.</font></div><d=
iv style=3D"background-color:rgba(0,0,0,0)!important;border-color:rgb(32,33=
,36)!important;color:rgb(255,255,255)!important" dir=3D"auto"><br></div><di=
v style=3D"background-color:rgba(0,0,0,0)!important;border-color:rgb(255,25=
5,255)!important;color:rgb(255,255,255)!important" dir=3D"auto"><font style=
=3D"border-color:rgb(0,0,0) rgb(0,0,0) rgb(0,0,0) rgb(204,204,204);color:rg=
b(0,0,0)">On the other hand, roughly every four years the coinbase reward h=
alves, which does significantly lower the miner budget, at least in terms o=
f BTC.</font></div><div dir=3D"auto"><span style=3D"border-color:rgb(0,0,0)=
 rgb(0,0,0) rgb(0,0,0) rgb(204,204,204);color:rgb(0,0,0)"><br></span></div>=
<div dir=3D"auto"><span style=3D"border-color:rgb(0,0,0) rgb(0,0,0) rgb(0,0=
,0) rgb(204,204,204);color:rgb(0,0,0)">Zac</span></div><div dir=3D"auto"><s=
pan style=3D"border-color:rgb(0,0,0) rgb(0,0,0) rgb(0,0,0) rgb(204,204,204)=
;color:rgb(0,0,0)"><br></span></div><div><span style=3D"border-color:rgb(0,=
0,0) rgb(0,0,0) rgb(0,0,0) rgb(204,204,204);color:rgb(0,0,0)"><br></span></=
div><div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_att=
r">On Sun, 16 May 2021 at 21:02, Karl via bitcoin-dev &lt;<a href=3D"mailto=
:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.linuxfoundation.o=
rg</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margi=
n:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;padding-l=
eft:1ex;border-left-color:rgb(204,204,204)">[sorry if I haven&#39;t replied=
 to the other thread on this, I get swamped<br>
by email and don&#39;t catch them all]<br>
<br>
This solution is workable but it seems somewhat difficult to me at this tim=
e.<br>
<br>
The clock might be implementable on a peer network level by requiring<br>
inclusion of a transaction that was broadcast after a 9 minute delay.<br>
<br>
Usually a 50% hashrate attack is needed to reverse a transaction in<br>
bitcoin.=C2=A0 With this change, this naively appears to become a 5%<br>
hashrate attack, unless a second source of truth around time and order<br>
is added, to verify proposed histories with.<br>
<br>
A 5% hashrate attack is much harder here, because the users of mining<br>
pools would be mining only 10% of the time, so compromising mining<br>
pools would not be as useful.<br>
<br>
Historically, hashrate has increased exponentially.=C2=A0 This means that<b=
r>
the difficulty of performing an attack, whether it is 5% or 50%, is<br>
still culturally infeasible because it is a multiplicative, rather<br>
than an exponential, change.<br>
<br>
If this approach were to be implemented, it could be important to<br>
consider how many block confirmations people wait for to trust their<br>
transaction is on the chain.=C2=A0 A lone powerful miner could<br>
intentionally fork the chain more easily by a factor of 10.=C2=A0 They<br>
would need to have hashrate that competes with a major pool to do so.<br>
<br>
&gt; How would you prevent miners to already compute the simpler difficulty=
 problem directly after the block was found and publish their solution dire=
ctly after minute 9? We would always have many people with a finished / com=
peting solution.<br>
<br>
Such a chain would have to wait a longer time to add further blocks<br>
and would permanently be shorter.<br>
<br>
&gt; Your proposal won=E2=80=99t save any energy because it does nothing to=
 decrease the budget available to mine a block (being the block reward).<br=
>
<br>
You are assuming this budget is directly related to energy<br>
expenditure, but if energy is only expended for 10% of the same<br>
duration, this money must now be spent on hardware.=C2=A0 The supply of<br>
bitcoin hardware is limited.<br>
<br>
In the long term, it won&#39;t be, so a 10% decrease is a stop-gap<br>
measure.=C2=A0 Additionally, in the long term, we will have quantum<br>
computers and AI-designed cryptography algorithms, so things will be<br>
different in a lot of other ways too.<br>
_______________________________________________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank">=
bitcoin-dev@lists.linuxfoundation.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation.org/mail=
man/listinfo/bitcoin-dev</a><br>
</blockquote></div></div>

--00000000000020f63e05c278fa4b--