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
|
Return-Path: <zachgrw@gmail.com>
Received: from smtp2.osuosl.org (smtp2.osuosl.org [IPv6:2605:bc80:3010::133])
by lists.linuxfoundation.org (Postfix) with ESMTP id 5742CC0001
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 16 May 2021 15:30:35 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by smtp2.osuosl.org (Postfix) with ESMTP id 2E4CC40244
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 16 May 2021 15:30:35 +0000 (UTC)
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001,
HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001]
autolearn=ham autolearn_force=no
Authentication-Results: smtp2.osuosl.org (amavisd-new);
dkim=pass (2048-bit key) header.d=gmail.com
Received: from smtp2.osuosl.org ([127.0.0.1])
by localhost (smtp2.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id MhnQOe5feRR9
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 16 May 2021 15:30:34 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.8.0
Received: from mail-io1-xd2b.google.com (mail-io1-xd2b.google.com
[IPv6:2607:f8b0:4864:20::d2b])
by smtp2.osuosl.org (Postfix) with ESMTPS id 287A840247
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 16 May 2021 15:30:33 +0000 (UTC)
Received: by mail-io1-xd2b.google.com with SMTP id i7so3427123ioa.12
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 16 May 2021 08:30:33 -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=9YVVo5TXb7qYp6TykCc7clFVABSCLo5Us0VyD1xL5Wc=;
b=qn0TIfFJgaWWAzpCyUn4yiFIRP/ZEe4hYWkBeQVar6IYxHVRfZ/kjT31/BadVzs6IM
snoXNJjsVDi+jDXZooLDv2HJbnwQQ+S3OK1t0920HOKUY6K6Ix3LmWThPaR11fQYvAhY
vf9DzGDsNNBg4riv+1GvSTWQG3uuK9xDVck4iJSBRCXrazcywTwRxgFpDEuc+lrF9Bfa
pnfurpQwvV0YxT1uk/BqPl7hI2WPifGudGPU0YPPkxSIXMPyWxgVJqBumONY1RGkNwRd
HNBefvl4rDJEdSHhVKdf0Yj8NKhRyPsOuKvSnZMUCPON+Xj2M2JmwoKW3/o0Dlinec6p
ekoQ==
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=9YVVo5TXb7qYp6TykCc7clFVABSCLo5Us0VyD1xL5Wc=;
b=gQm8saMjZ1U5Sfo6vkhQ6kEOiE/Jkr6peTZG1+IsYBbp0znfmvqcSIugA2ozpkH44q
4Vgs41qISVaH8+qV93AQ9PxHFK8axyVGbdEtC3O0Kpjm72LDHnlIgg2Scs5A6ehnHL2Y
kAmZl2bsfDi6v/SeHksjIsjkS7NPpTIx9tkiJpZAsZgE3962ctAPA/keeehtllqgTJ9e
ezwBYd5DvjA5vgQapRIKVlQcOxhCY0d2s5QQWCy9GBTavJetBxDrOkbhr6HEO6UJpNIx
3C2snATtaNLGARsFTB3QI918WlMbCqgIT4lWjj0AvddHuS6v4z9Ns1Dh+/BXG6SaukGy
4qdQ==
X-Gm-Message-State: AOAM532px8RnsV86CuwH5IaHxlsSgjq55YAgEiD/HRoMUH0ZiYG24haY
QFB44h2u0T5Iw07cddeokJWfam8px6w5Ug8V9WyJlDeU
X-Google-Smtp-Source: ABdhPJxf9CjZ1RCm0oDbxgnmtiyYMPDvTxOeIam8w2y6BPD5ct2R74+/XnoXb1auouWfgdbjX21XJApPxiFrgP2EuUI=
X-Received: by 2002:a05:6638:1242:: with SMTP id
o2mr52318016jas.10.1621179033322;
Sun, 16 May 2021 08:30:33 -0700 (PDT)
MIME-Version: 1.0
References: <d35dee03-2d19-e80a-c577-2151938f9203@web.de>
In-Reply-To: <d35dee03-2d19-e80a-c577-2151938f9203@web.de>
From: Zac Greenwood <zachgrw@gmail.com>
Date: Sun, 16 May 2021 17:30:22 +0200
Message-ID: <CAJ4-pEDbtGpc4+NrrKga9N79YQjK1=zTEPN9V2G18NEnZ1h1YA@mail.gmail.com>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>,
Michael Fuhrmann <fuhmic@web.de>
Content-Type: multipart/alternative; boundary="00000000000066084f05c2742872"
X-Mailman-Approved-At: Sun, 16 May 2021 15:52:50 +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 15:30:35 -0000
--00000000000066084f05c2742872
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Hi Michael,
Your proposal won=E2=80=99t save any energy because it does nothing to decr=
ease the
budget available to mine a block (being the block reward).
Even if it were technically possible to find a way for nodes to somehow
reach consensus on a hash that gets generated after 9 minutes, all it
achieves is that miners will be expending the entire budget given to them
in the form of the block reward within a single minute on average.
Also please realize that the energy expenditure of Bitcoin is a fundamental
part of its design. An attacker has no other option than to expend as much
as half of all the miners together do in order for a sustained 51% attack
to be successful, making such attack uneconomical.
Zac
On Sat, 15 May 2021 at 23:57, Michael Fuhrmann via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:
> Hello,
>
> Bitcoin should create blocks every 10 minutes in average. So why do
> miners need to mine the 9 minutes after the last block was found? It's
> not necessary.
>
> Problem: How to prevent "pre-mining" in the 9 minutes time window?
>
> Possible ideas for discussion:
>
> - (maybe most difficult) global network timer sending a salted hash time
> code after 9 minutes. this enables validation by nodes.
>
> - (easy attempt) mining jobs before 9 minutes have a 10 (or 100 or just
> high enough) times higher difficulty. so everyone can mine any time but
> before to 9 minutes are up there will be a too high downside. It is more
> efficient to wait then paying high bills. The bitcoin will get a "puls".
>
>
> I dont think I see all problems behind these ideas but if there is a
> working solution to do so then the energy fud will find it's end. Saving
> energy without loosing rosbustness.
>
>
>
> :)
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
--00000000000066084f05c2742872
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"auto">Hi Michael,</div><div dir=3D"auto"><br></div><div dir=3D"=
auto">Your proposal won=E2=80=99t save any energy because it does nothing t=
o decrease the budget available to mine a block (being the block reward).</=
div><div dir=3D"auto"><br></div><div dir=3D"auto">Even if it were technical=
ly possible to find a way for nodes to somehow reach consensus on a hash th=
at gets generated after 9 minutes, all it achieves is that miners will be e=
xpending the entire budget given to them in the form of the block reward wi=
thin a single minute on average.</div><div dir=3D"auto"><br></div><div dir=
=3D"auto">Also please realize that the energy expenditure of Bitcoin is a f=
undamental part of its design. An attacker has no other option than to expe=
nd as much as half of all the miners together do in order for a sustained 5=
1% attack to be successful, making such attack uneconomical.</div><div dir=
=3D"auto"><br></div><div dir=3D"auto">Zac</div><div><br><div class=3D"gmail=
_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Sat, 15 May 2021 at 23:57,=
Michael Fuhrmann via bitcoin-dev <<a href=3D"mailto:bitcoin-dev@lists.l=
inuxfoundation.org">bitcoin-dev@lists.linuxfoundation.org</a>> wrote:<br=
></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;=
border-left-width:1px;border-left-style:solid;padding-left:1ex;border-left-=
color:rgb(204,204,204)">Hello,<br>
<br>
Bitcoin should create blocks every 10 minutes in average. So why do<br>
miners need to mine the 9 minutes after the last block was found? It's<=
br>
not necessary.<br>
<br>
Problem: How to prevent "pre-mining" in the 9 minutes time window=
?<br>
<br>
Possible ideas for discussion:<br>
<br>
- (maybe most difficult) global network timer sending a salted hash time<br=
>
code after 9 minutes. this enables validation by nodes.<br>
<br>
- (easy attempt) mining jobs before 9 minutes have a 10 (or 100 or just<br>
high enough) times higher difficulty. so everyone can mine any time but<br>
before to 9 minutes are up there will be a too high downside. It is more<br=
>
efficient to wait then paying high bills. The bitcoin will get a "puls=
".<br>
<br>
<br>
I dont think I see all problems behind these ideas but if there is a<br>
working solution to do so then the energy fud will find it's end. Savin=
g<br>
energy without loosing rosbustness.<br>
<br>
<br>
<br>
:)<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>
--00000000000066084f05c2742872--
|