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
|
Return-Path: <r.pickhardt@googlemail.com>
Received: from smtp2.osuosl.org (smtp2.osuosl.org [140.211.166.133])
by lists.linuxfoundation.org (Postfix) with ESMTP id 38657C0001
for <bitcoin-dev@lists.linuxfoundation.org>;
Sat, 15 May 2021 22:14:27 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by smtp2.osuosl.org (Postfix) with ESMTP id 278E2401CD
for <bitcoin-dev@lists.linuxfoundation.org>;
Sat, 15 May 2021 22:14:27 +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=googlemail.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 XQsMddL2oyKU
for <bitcoin-dev@lists.linuxfoundation.org>;
Sat, 15 May 2021 22:14:26 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.8.0
Received: from mail-wr1-x42f.google.com (mail-wr1-x42f.google.com
[IPv6:2a00:1450:4864:20::42f])
by smtp2.osuosl.org (Postfix) with ESMTPS id F1268400E2
for <bitcoin-dev@lists.linuxfoundation.org>;
Sat, 15 May 2021 22:14:25 +0000 (UTC)
Received: by mail-wr1-x42f.google.com with SMTP id r12so2594579wrp.1
for <bitcoin-dev@lists.linuxfoundation.org>;
Sat, 15 May 2021 15:14:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=googlemail.com; s=20161025;
h=mime-version:references:in-reply-to:from:date:message-id:subject:to;
bh=+JKkUMzw9rpGPFvFBabvj77Qf2UhSdzuL9nfyUoyc6k=;
b=M1hsxgrcRjnEli0i88FtEiKJR0oRlwkGsXlI7/3u2syZ11Gp4t7YuOzoBOHnxti1jK
2NXTnnAwYb3tKzZWY9cRQBbHN2cOH3lBHFqyBKGSQaFQyaBGnFqEUfpNJSdSiViNtPS4
EoJj3Shqlkgw1LIetPWOj1eNCX1kn2YjMGVGDICx5TPRMxjIIUevFOndKGCYCJ2HaVoL
UmAx7EyKWqznefJVH21HfshA0afouTi78FqM/iDk1VxLMLTS0WV6KA096TyKXYRtwVbW
K6GZuTECVEagZVdRVr/ZS7YU41Looo5lnZ9zcFyk2DQ8XcPrkx+l9kXkkB4wHveK4OoM
acew==
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=+JKkUMzw9rpGPFvFBabvj77Qf2UhSdzuL9nfyUoyc6k=;
b=kZZiuSP2VtqU/MfCciS2DNivrC959YxZqxpgrpF3vHCsGzVglO8269YDz/WHxeUKJR
4OPZrSt1/QKe9UdyZEwk9lRVdznhLEJNcvUtXOIAGfIyEZxvcUOX1AF7ihvfEhv2kNVj
1j9+FH4Z4n5Vg3QJT0RTV2QYh7ooB0jWFOImUnFpTtwSW/qBVwl8zYocfKK33hlo6Sn7
Vk5td3ByKhDcrnhD0r5BlMRBMJD32J+cjIHFIO+slj4UxlbeKr5BaWwULNrfl1hb8WH/
/epeZN+EQ0xqTFWswUN9lu9/wl2EpdXZHu+PTiOhJsiQ+EkRRuJBhI/oZZuThTy/2iTj
9Igw==
X-Gm-Message-State: AOAM530td9B1bnfxPeTod9FrVuH8bz7grEZ6GD7SoUFpWW7gFgIxpT2M
beVGxr3Jw1xr3sm1IW8GoXCQ3/E1NzzmLwx9E6U=
X-Google-Smtp-Source: ABdhPJzxmYbIh6D4CTVFd5I85CoXwCzlRB/yzvycUF1ymwOwiuVMS1uTXKMj2+autIhAcPnB3WbHjhSV/AYZq/a7SjQ=
X-Received: by 2002:a5d:6248:: with SMTP id m8mr66204742wrv.42.1621116864202;
Sat, 15 May 2021 15:14:24 -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: =?UTF-8?Q?Ren=C3=A9_Pickhardt?= <r.pickhardt@googlemail.com>
Date: Sun, 16 May 2021 00:14:13 +0200
Message-ID: <CAJ5H3Z5C_Rjszb1QgGqhJa5F2_ts4CoT=1c0=efBcK8D96Svdw@mail.gmail.com>
To: Michael Fuhrmann <fuhmic@web.de>,
Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary="000000000000d4885c05c265aecd"
X-Mailman-Approved-At: Sat, 15 May 2021 22:28:49 +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: Sat, 15 May 2021 22:14:27 -0000
--000000000000d4885c05c265aecd
Content-Type: text/plain; charset="UTF-8"
Hey Michael,
First I think the idea of "do nothing in the first 9 minutes" will
unfortunately not be useful as the computed work is mainly there to prevent
miners from altering the history of previous blocks. Thus following your
suggesting would probably drastically decease the security of the network
as less work protects previously mined blocks allowing for lower cost to
compute a reorg.
Let us assume the aforementioned point could somehow be resolved there
would be another practical issue. It is hard / impossible to sync clocks in
a distributed network which I think would be necessary for a system that
you propose. (actually Bitcoin is one way of introducing a temporal
ordering of events in a distributed network)
Finally even if that was also resolved: 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.
So while I appreciate the idea I have the feeling it would be impractical
but maybe I missed something.
Best Rene
Michael Fuhrmann via bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org>
schrieb am Sa., 15. Mai 2021, 23:57:
> 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
>
--000000000000d4885c05c265aecd
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"auto">Hey Michael,<div dir=3D"auto"><br></div><div dir=3D"auto"=
>First I think the idea of "do nothing in the first 9 minutes" wi=
ll unfortunately not be useful as the computed work is mainly there to prev=
ent miners from altering the history of previous blocks. Thus following you=
r suggesting would probably drastically decease the security of the network=
as less work protects previously mined blocks allowing for lower cost to c=
ompute a reorg.=C2=A0</div><div dir=3D"auto"><br></div><div dir=3D"auto"><b=
r></div><div dir=3D"auto">Let us assume the aforementioned point could some=
how be resolved there would be another practical issue. It is hard / imposs=
ible to sync clocks in a distributed network which I think would be necessa=
ry for a system that you propose. (actually Bitcoin is one way of introduci=
ng a temporal ordering of events in a distributed network)=C2=A0</div><div =
dir=3D"auto"><br></div><div dir=3D"auto">Finally even if that was also reso=
lved: How would you prevent miners to already compute the simpler difficult=
y problem directly after the block was found and publish their solution dir=
ectly after minute 9? We would always have many people with a finished / co=
mpeting solution.</div><div dir=3D"auto"><br></div><div dir=3D"auto">So whi=
le I appreciate the idea I have the feeling it would be impractical but may=
be I missed something.</div><div dir=3D"auto"><br></div><div dir=3D"auto">B=
est Rene</div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=
=3D"gmail_attr">Michael Fuhrmann via bitcoin-dev <<a href=3D"mailto:bitc=
oin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.linuxfoundation.org</a=
>> schrieb am Sa., 15. Mai 2021, 23:57:<br></div><blockquote class=3D"gm=
ail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-le=
ft:1ex">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" =
rel=3D"noreferrer">bitcoin-dev@lists.linuxfoundation.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer noreferrer" target=3D"_blank">https://lists.linuxfoundati=
on.org/mailman/listinfo/bitcoin-dev</a><br>
</blockquote></div>
--000000000000d4885c05c265aecd--
|