summaryrefslogtreecommitdiff
path: root/c7/0099d2f11f1ae56dfd681d9af64eb6f324643e
blob: 47f12a869aca245b12bd32ef1ba77ffaa4a2fe42 (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
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
Return-Path: <loneroassociation@gmail.com>
Received: from smtp3.osuosl.org (smtp3.osuosl.org [140.211.166.136])
 by lists.linuxfoundation.org (Postfix) with ESMTP id 55971C0001
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Mon, 15 Mar 2021 02:59:00 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by smtp3.osuosl.org (Postfix) with ESMTP id 372316F4A4
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Mon, 15 Mar 2021 02:59:00 +0000 (UTC)
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 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_HELO_NONE=0.001,
 SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: smtp3.osuosl.org (amavisd-new);
 dkim=pass (2048-bit key) header.d=gmail.com
Received: from smtp3.osuosl.org ([127.0.0.1])
 by localhost (smtp3.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id gJcw67oRNbKQ
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Mon, 15 Mar 2021 02:58:58 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.8.0
Received: from mail-yb1-xb35.google.com (mail-yb1-xb35.google.com
 [IPv6:2607:f8b0:4864:20::b35])
 by smtp3.osuosl.org (Postfix) with ESMTPS id 5ABEB6F49F
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Mon, 15 Mar 2021 02:58:58 +0000 (UTC)
Received: by mail-yb1-xb35.google.com with SMTP id l8so31712128ybe.12
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Sun, 14 Mar 2021 19:58:58 -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
 :cc; bh=7o+gONtTP7hCG5xgTI4uoYerFPCP6GhfhhGD23tUSN8=;
 b=BltDH1xg53u9ga2kfrM9O5pi+5lJk0Omn0LjwRyz+SbnWi9N2A+6ErjXAKGqJTCR28
 27nVrpQHxyelmVKCd75/4lxN/0lU0f+Ia0zODt6awYrh3oBvhzimReZER010zA8z+Ulm
 Gbooq9PVLnOwXsAiCKJva4htltC3uZQPzGwMNI2tMWzooOya8rNAaFkxiB9NmJqfEVMy
 srBK6wl79AGBver0y37mWEfknFqVHiC72Dtyn80XrjW2ui7nl6c2jfBcqPE83phsc/7l
 qrSn8FDADlHNg3CIO4z94wGT2x1oDfhGddo1Y+Iidp/TwpHuNoI8ik+3RW61E6LGpA50
 DDnA==
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:cc;
 bh=7o+gONtTP7hCG5xgTI4uoYerFPCP6GhfhhGD23tUSN8=;
 b=kBMWQoBWxNTdPp2d4pKR3FqkVBi8iiZsJZJlDyjXknH6T13HUhm4UWCHqFKtljPPRx
 N+PJKXpNG0eDAMugqX+63VmAiiTx/bH/uSsWjtPVR/3E3Bk1pIS7x88ipOrkWScEd+6D
 LlMtNUSigz8iGUqHNHL570EJ/iRFhzEk7G/cywHeNuxfJG049UxI7Ok7Lsauk1FSF5pB
 vc69y12VgHVcEKdvRH5VKCP4mpRdQRQ9NWsVhcqBxSocqH77cjFWT0eGIuyu74ZhrzOn
 bbnqI/sR6mImxObwTMIH2XBYbwFCke67vfGuaKWNXy1+K8uZmbrjcgIv9J8GyWUJqiOJ
 2sdg==
X-Gm-Message-State: AOAM530to/v/B94Zs9AqWkB1CZhHYHnMCVeeSUuy+Aswr+9g3IjHxUi8
 jhsFZq+GL8v3DUtaMgYgzLvXKSU/o5hGWrP521Y=
X-Google-Smtp-Source: ABdhPJxbhXPCwSACEyryhrlStGKw+tuEHtg+CawmLwzlX7HgwBx6vCanWHwE78R5cxAuYszteapxwa15TWj/K5P0D1o=
X-Received: by 2002:a25:b206:: with SMTP id i6mr32955709ybj.499.1615777137286; 
 Sun, 14 Mar 2021 19:58:57 -0700 (PDT)
MIME-Version: 1.0
References: <CA+YkXXxUdZFYTa1c-F=-FzoQQVtV3GUmE2Okec-zRAD3xS1qAQ@mail.gmail.com>
 <CAMnpzfop8ttqjMAKoS37zpQV6WiZfi1Bn+y_e-HaepTiD4Vm1Q@mail.gmail.com>
 <CAB0O3SVNyr_t23Y0LyT0mSaf6LONFRLYJ8qzO7rcdJFnrGccFw@mail.gmail.com>
 <CA+YkXXwkSCu=2UOEhzFBzGDHo1c=Ewqsnxp632ke3jdH1ff5WA@mail.gmail.com>
 <CA+YkXXwfS7eer5Za_ed9tCNdfOp4c3nV_X=mfXzoDxMm6BrizQ@mail.gmail.com>
 <PS2P216MB0914F0B05E1AAB48D9A765609D6D9@PS2P216MB0914.KORP216.PROD.OUTLOOK.COM>
 <CAAf19Wq+v_2UjxHn8eBuBcL+mgNbD9joQ8eTV6O1+LuDwX=Fng@mail.gmail.com>
 <CA+YkXXxN8G6NELXwr_d+_iuqJkBQT5_EBbcOvZhy6iPuURz9bA@mail.gmail.com>
 <CA+YkXXyMUQtdSvjuMPQO71LpPb8qFdy-LTSrA8FEbeWMbPWa4w@mail.gmail.com>
In-Reply-To: <CA+YkXXyMUQtdSvjuMPQO71LpPb8qFdy-LTSrA8FEbeWMbPWa4w@mail.gmail.com>
From: Lonero Foundation <loneroassociation@gmail.com>
Date: Sun, 14 Mar 2021 22:58:45 -0400
Message-ID: <CA+YkXXyb+ajOY237Q==NOWqOnbMARZ=54_GF62rMMo2XBk-U-A@mail.gmail.com>
To: Eric Martindale <eric@ericmartindale.com>
Content-Type: multipart/alternative; boundary="0000000000004ddf5a05bd8a6ea3"
X-Mailman-Approved-At: Tue, 16 Mar 2021 13:22:59 +0000
Cc: Devrandom <c1.devrandom@niftybox.net>,
 Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] BIP Proposal: Consensus (hard fork) PoST
 Datastore for Energy Efficient Mining
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: Mon, 15 Mar 2021 02:59:00 -0000

--0000000000004ddf5a05bd8a6ea3
Content-Type: text/plain; charset="UTF-8"

Actually disregard my last email, I realize you were replying to somebody
else instead of me. Please for proposals not related to my BIP, such as a
form of "luck chance lottery", post in a different discussion thread as to
not draw confusion.

Best regards, Andrew

On Sun, Mar 14, 2021, 10:51 PM Lonero Foundation <
loneroassociation@gmail.com> wrote:

> I also want to emphasize that Bitcoin's energy consumption is growing at
> an exponential rate because of complexity. That in itself is a good thing
> security-wise. However, there are limitations to the cryptography it is
> using and the efficiency it is going about mining the way it is currently
> done.
>
> Bitcoin can have this massive carbon footprint all become meaningless if
> there is better math. So far we already outpaced many of the the more
> traditional forms of cryptographic protocols Bitcoin is currently using,
> including both for its mining and key validation. The hardware specificness
> is also too limited.
>
> My proposal doesn't redesign the way Bitcoin is structured or its system,
> rather it focuses on improvement or replacing what is outdated, and making
> it more resistant to centralization, forced monopolization or an attack.
>
> On Sun, Mar 14, 2021, 10:32 PM Lonero Foundation <
> loneroassociation@gmail.com> wrote:
>
>> Hi, just to clarify this isn't a trade-off on security. Infact, my
>> proposal actually increases the level of security that Bitcoin currently
>> has. There is both an efficiency and cryptography aspect to this proposal.
>> I talked about the higher levels of security a bit in my BIP, and have
>> talked to a few about energy consumption.
>>
>> Outside of consumption of energy however, is the fact that BTC can be
>> more adaptable towards a major range of hardware without disenfranchising
>> others or other major trade-offs. There is no need for BTC to specifically
>> be tailored towards ASICs if the same level of proof of work can be done
>> from other hardware sources at similar costs. The technology and level of
>> cryptography between now and when Satoshi started BTC development 14 years
>> ago is also fastly different. BTC went from you can mine lots of Bitcoin by
>> literally downloading the whitepaper, to USB miners, to ASICs to now whole
>> entire mining centers.
>>
>> This is because of complexity, but that complexity in the near future can
>> be entirely meaningless if it is vulnerable to some of the things many
>> cryptography experts are worried about. Keep in mind this is in draft mode,
>> but over time as further implementation is done, alot of the community
>> including yourself might start being impressed by the more and more
>> tangible results.
>>
>> Best regards, Andrew
>>
>> On Sun, Mar 14, 2021, 10:02 PM Eric Martindale <eric@ericmartindale.com>
>> wrote:
>>
>>> Bitcoin's security is derived from the energy consumption of mining, so
>>> reducing the overall expenditure would be an objective decrease in
>>> resilience.  As a miner, your efficiency at converting energy into
>>> hashpower is the driving factor in your profitability, so this and any
>>> other future attempts to decrease the cost of attacking Bitcoin receives a
>>> hard NACK from me.
>>>
>>> If you're concerned about missing out on the subsidy or fee revenue,
>>> grab any number of the sub-500mSAT USB miners and get access to cheap power.
>>>
>>> Sincerely,
>>>
>>> Eric Martindale, relentless maker.
>>> Founder & CEO, Fabric, Inc. <https://fabric.fm>
>>> +1 (919) 374-2020
>>>
>>>
>>> On Sun, Mar 14, 2021 at 9:41 AM LORD HIS EXCELLENCY JAMES HRMH via
>>> bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org> wrote:
>>>
>>>> Good Afternoon,
>>>>
>>>> It is obvious that something needs to be done to curtail the current
>>>> cost of mining in kWh per block. I understand proposals are rejected
>>>> because it is considered censorship and Bitcoin has a consensus to allow
>>>> anyone to mine but, since mining requires specific hardware and energy
>>>> requirements it is already a form of censorship where most on the planet
>>>> except for the top 6% I am guessing here, cannot afford to mine. Without
>>>> affecting the current algorithm, I have previously begun to explore the
>>>> process by which mining can be turned into a lottery with only authorized
>>>> payto addresses able to mine valid blocks, since transaction fees and block
>>>> rewards exist to pay the miner. It would be better even if the algorithms
>>>> are improved if there are some ways that only a subset of miners can
>>>> produce valid blocks for any given period, say for 12 months with four
>>>> groups starting three months apart to transition, and maybe limit mining to
>>>> 50 people per continent to produce valid blocks at any one time. Possibly
>>>> this requires a consortium to oversee the lottery but it is something
>>>> Bitcoin can handle themselves, and would do better to handle than to wait
>>>> for government intervention as we have seen previously in China where power
>>>> was too cheap Bitcoin was banned entirely.
>>>>
>>>> KING JAMES HRMH
>>>> Great British Empire
>>>>
>>>> Regards,
>>>> The Australian
>>>> LORD HIS EXCELLENCY JAMES HRMH (& HMRH)
>>>> of Hougun Manor & Glencoe & British Empire
>>>> MR. Damian A. James Williamson
>>>> Wills
>>>>
>>>> et al.
>>>>
>>>>
>>>> Willtech
>>>> www.willtech.com.au
>>>> www.go-overt.com
>>>> and other projects
>>>>
>>>> earn.com/willtech
>>>> linkedin.com/in/damianwilliamson
>>>>
>>>>
>>>> m. 0487135719
>>>> f. +61261470192
>>>>
>>>>
>>>> This email does not constitute a general advice. Please disregard this
>>>> email if misdelivered.
>>>> ------------------------------
>>>> *From:* bitcoin-dev <bitcoin-dev-bounces@lists.linuxfoundation.org> on
>>>> behalf of Lonero Foundation via bitcoin-dev <
>>>> bitcoin-dev@lists.linuxfoundation.org>
>>>> *Sent:* Saturday, 6 March 2021 3:16 AM
>>>> *To:* Devrandom <c1.devrandom@niftybox.net>
>>>> *Cc:* Bitcoin Protocol Discussion <
>>>> bitcoin-dev@lists.linuxfoundation.org>
>>>> *Subject:* Re: [bitcoin-dev] BIP Proposal: Consensus (hard fork) PoST
>>>> Datastore for Energy Efficient Mining
>>>>
>>>> Also in regards to my other email, I forgot to iterate that my
>>>> cryptography proposal helps behind the efficiency category but also tackles
>>>> problems such as NP-Completeness or Halting which is something the BTC
>>>> network could be vulnerable to in the future. For sake of simplicity, I do
>>>> want to do this BIP because it tackles lots of the issues in regards to
>>>> this manner and can provide useful insight to the community. If things such
>>>> as bigger block height have been proposed as hard forks, I feel at the very
>>>> least an upgrade regarding the hashing algorithm and cryptography does at
>>>> least warrant some discussion. Anyways I hope I can send you my BIP, just
>>>> let me know on the preferred format?
>>>>
>>>> Best regards, Andrew
>>>>
>>>> On Fri, Mar 5, 2021, 10:12 AM Lonero Foundation <
>>>> loneroassociation@gmail.com> wrote:
>>>>
>>>> Hi, this isn't about the energy efficient argument in regards to
>>>> renewables or mining devices but a better cryptography layer to get the
>>>> most out of your hashing for validation. I do understand the arbitrariness
>>>> of it, but do want to still propose a document. Do I use the Media Wiki
>>>> format on GitHub and just attach it as my proposal?
>>>>
>>>> Best regards, Andrew
>>>>
>>>> On Fri, Mar 5, 2021, 10:07 AM Devrandom <c1.devrandom@niftybox.net>
>>>> wrote:
>>>>
>>>> Hi Ryan and Andrew,
>>>>
>>>> On Fri, Mar 5, 2021 at 5:42 AM Ryan Grant via bitcoin-dev <
>>>> bitcoin-dev@lists.linuxfoundation.org> wrote:
>>>>
>>>>
>>>>   https://www.truthcoin.info/blog/pow-cheapest/
>>>>     "Nothing is Cheaper than Proof of Work"
>>>>     on | 04 Aug 2015
>>>>
>>>>
>>>> Just to belabor this a bit, the paper demonstrates that the mining
>>>> market will tend to expend resources equivalent to miner reward.  It does
>>>> not prove that mining work has to expend *energy* as a primary cost.
>>>>
>>>> Some might argue that energy expenditure has negative externalities and
>>>> that we should move to other resources.  I would argue that the negative
>>>> externalities will go away soon because of the move to renewables, so the
>>>> point is likely moot.
>>>>
>>>> _______________________________________________
>>>> bitcoin-dev mailing list
>>>> bitcoin-dev@lists.linuxfoundation.org
>>>> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>>>>
>>>

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

<div dir=3D"auto">Actually disregard my last email, I realize you were repl=
ying to somebody else instead of me. Please for proposals not related to my=
 BIP, such as a form of &quot;luck chance lottery&quot;, post in a differen=
t discussion thread as to not draw confusion.<div dir=3D"auto"><br></div><d=
iv dir=3D"auto">Best regards, Andrew</div></div><br><div class=3D"gmail_quo=
te"><div dir=3D"ltr" class=3D"gmail_attr">On Sun, Mar 14, 2021, 10:51 PM Lo=
nero Foundation &lt;<a href=3D"mailto:loneroassociation@gmail.com">loneroas=
sociation@gmail.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quot=
e" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">=
<div dir=3D"auto">I also want to emphasize that Bitcoin&#39;s energy consum=
ption is growing at an exponential rate because of complexity. That in itse=
lf is a good thing security-wise. However, there are limitations to the cry=
ptography it is using and the efficiency it is going about mining the way i=
t is currently done.=C2=A0<div dir=3D"auto"><br></div><div dir=3D"auto">Bit=
coin can have this massive carbon footprint all become meaningless if there=
 is better math. So far we already outpaced many of the the more traditiona=
l forms of cryptographic protocols Bitcoin is currently using, including bo=
th for its mining and key validation. The hardware specificness is also too=
 limited.</div><div dir=3D"auto"><br></div><div dir=3D"auto">My proposal do=
esn&#39;t redesign the way Bitcoin is structured or its system, rather it f=
ocuses on improvement or replacing what is outdated, and making it more res=
istant to centralization, forced monopolization or an attack.</div></div><b=
r><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Sun, =
Mar 14, 2021, 10:32 PM Lonero Foundation &lt;<a href=3D"mailto:loneroassoci=
ation@gmail.com" rel=3D"noreferrer noreferrer noreferrer" target=3D"_blank"=
>loneroassociation@gmail.com</a>&gt; wrote:<br></div><blockquote class=3D"g=
mail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-l=
eft:1ex"><div dir=3D"auto">Hi, just to clarify this isn&#39;t a trade-off o=
n security. Infact, my proposal actually increases the level of security th=
at Bitcoin currently has. There is both an efficiency and cryptography aspe=
ct to this proposal. I talked about the higher levels of security a bit in =
my BIP, and have talked to a few about energy consumption.=C2=A0<div dir=3D=
"auto"><br></div><div dir=3D"auto">Outside of consumption of energy however=
, is the fact that BTC can be more adaptable towards a major range of hardw=
are without disenfranchising others or other major trade-offs. There is no =
need for BTC to specifically be tailored towards ASICs if the same level of=
 proof of work can be done from other hardware sources at similar costs. Th=
e technology and level of cryptography between now and when Satoshi started=
 BTC development 14 years ago is also fastly different. BTC went from you c=
an mine lots of Bitcoin by literally downloading the whitepaper, to USB min=
ers, to ASICs to now whole entire mining centers.=C2=A0</div><div dir=3D"au=
to"><br></div><div dir=3D"auto">This is because of complexity, but that com=
plexity in the near future can be entirely meaningless if it is vulnerable =
to some of the things many cryptography experts are worried about. Keep in =
mind this is in draft mode, but over time as further implementation is done=
, alot of the community including yourself might start being impressed by t=
he more and more tangible results.<div dir=3D"auto"><br></div><div dir=3D"a=
uto">Best regards, Andrew</div></div></div><br><div class=3D"gmail_quote"><=
div dir=3D"ltr" class=3D"gmail_attr">On Sun, Mar 14, 2021, 10:02 PM Eric Ma=
rtindale &lt;<a href=3D"mailto:eric@ericmartindale.com" rel=3D"noreferrer n=
oreferrer noreferrer noreferrer" target=3D"_blank">eric@ericmartindale.com<=
/a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0=
 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr">Bit=
coin&#39;s security is derived from the energy consumption of mining, so re=
ducing the overall expenditure would be an objective decrease in resilience=
.=C2=A0 As a miner, your efficiency at converting energy into hashpower is =
the driving factor in your profitability, so this and any other future atte=
mpts to decrease the cost of attacking Bitcoin receives a hard NACK from me=
.<br><br>If you&#39;re concerned about missing out on the subsidy=C2=A0or f=
ee revenue, grab any number of the sub-500mSAT USB miners and get access to=
 cheap power.<br><br>Sincerely,<br><br clear=3D"all"><div><div dir=3D"ltr" =
data-smartmail=3D"gmail_signature"><div dir=3D"ltr"><div><div dir=3D"ltr"><=
div style=3D"color:rgb(33,33,33);font-family:&quot;Helvetica Neue&quot;,Hel=
vetica,Arial,sans-serif;font-size:13px;line-height:19.5px">Eric Martindale,=
 relentless maker.</div><div style=3D"color:rgb(33,33,33);font-family:&quot=
;Helvetica Neue&quot;,Helvetica,Arial,sans-serif;font-size:13px;line-height=
:19.5px">Founder &amp; CEO, <a href=3D"https://fabric.fm" rel=3D"noreferrer=
 noreferrer noreferrer noreferrer noreferrer" target=3D"_blank">Fabric, Inc=
.</a></div><div style=3D"color:rgb(33,33,33);font-family:&quot;Helvetica Ne=
ue&quot;,Helvetica,Arial,sans-serif;font-size:13px;line-height:19.5px">+1 (=
919) 374-2020</div></div></div></div></div></div><br></div><br><div class=
=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Sun, Mar 14, 2021=
 at 9:41 AM LORD HIS EXCELLENCY JAMES HRMH via bitcoin-dev &lt;<a href=3D"m=
ailto:bitcoin-dev@lists.linuxfoundation.org" rel=3D"noreferrer noreferrer n=
oreferrer noreferrer noreferrer" target=3D"_blank">bitcoin-dev@lists.linuxf=
oundation.org</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);paddi=
ng-left:1ex">




<div dir=3D"ltr">
<div style=3D"font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color=
:rgb(0,0,0)">
</div>
<span style=3D"font-family:Cantarell;font-size:14.6667px;font-weight:normal=
;text-align:left;background-color:rgb(255,255,255)">Good Afternoon,</span>
<div style=3D"font-family:Cantarell;font-size:14.6667px;font-weight:normal;=
text-align:left;background-color:rgb(255,255,255)">
<br>
</div>
<div style=3D"font-family:Cantarell;font-size:14.6667px;font-weight:normal;=
text-align:left;background-color:rgb(255,255,255)">
It is obvious that something needs to be done to curtail the current cost o=
f mining in kWh per block. I understand proposals are rejected because it i=
s considered censorship and Bitcoin has a consensus to allow anyone to mine=
 but, since mining requires specific
 hardware and energy requirements it is already a form of censorship where =
most on the planet except for the top 6% I am guessing here, cannot afford =
to mine. Without affecting the current algorithm, I have previously begun t=
o explore the process by which mining
 can be turned into a lottery with only authorized payto addresses able to =
mine valid blocks, since transaction fees and block rewards exist to pay th=
e miner. It would be better even if the algorithms are improved if there ar=
e some ways that only a subset of
 miners can produce valid blocks for any given period, say for 12 months wi=
th four groups starting three months apart to transition, and maybe limit m=
ining to 50 people per continent to produce valid blocks at any one time. P=
ossibly this requires a consortium
 to oversee the lottery but it is something Bitcoin can handle themselves, =
and would do better to handle than to wait for government intervention as w=
e have seen previously in China where power was too cheap Bitcoin was banne=
d entirely.</div>
<div style=3D"font-family:Cantarell;font-size:14.6667px;font-weight:normal;=
text-align:left;background-color:rgb(255,255,255)">
<br>
</div>
<div style=3D"font-family:Cantarell;font-size:14.6667px;font-weight:normal;=
text-align:left;background-color:rgb(255,255,255)">
KING JAMES HRMH</div>
<div style=3D"font-family:Cantarell;font-size:14.6667px;font-weight:normal;=
text-align:left;background-color:rgb(255,255,255)">
Great British Empire</div>
<div style=3D"font-family:Cantarell;font-size:14.6667px;font-weight:normal;=
text-align:left;background-color:rgb(255,255,255)">
<br>
</div>
<div style=3D"font-family:Cantarell;font-size:14.6667px;font-weight:normal;=
text-align:left;background-color:rgb(255,255,255)">
Regards,</div>
<div style=3D"font-family:Cantarell;font-size:14.6667px;font-weight:normal;=
text-align:left;background-color:rgb(255,255,255)">
The Australian</div>
<div style=3D"font-family:Cantarell;font-size:14.6667px;font-weight:normal;=
text-align:left;background-color:rgb(255,255,255)">
LORD HIS EXCELLENCY JAMES HRMH (&amp; HMRH)</div>
<div style=3D"font-family:Cantarell;font-size:14.6667px;font-weight:normal;=
text-align:left;background-color:rgb(255,255,255)">
of Hougun Manor &amp; Glencoe &amp; British Empire</div>
<div style=3D"font-family:Cantarell;font-size:14.6667px;font-weight:normal;=
text-align:left;background-color:rgb(255,255,255)">
MR. Damian A. James Williamson</div>
<div style=3D"font-family:Cantarell;font-size:14.6667px;font-weight:normal;=
text-align:left;background-color:rgb(255,255,255)">
Wills</div>
<div style=3D"font-family:Cantarell;font-size:14.6667px;font-weight:normal;=
text-align:left;background-color:rgb(255,255,255)">
<br>
</div>
<div style=3D"font-family:Cantarell;font-size:14.6667px;font-weight:normal;=
text-align:left;background-color:rgb(255,255,255)">
et al.</div>
<div style=3D"font-family:Cantarell;font-size:14.6667px;font-weight:normal;=
text-align:left;background-color:rgb(255,255,255)">
<br>
</div>
<div style=3D"font-family:Cantarell;font-size:14.6667px;font-weight:normal;=
text-align:left;background-color:rgb(255,255,255)">
=C2=A0</div>
<div style=3D"font-family:Cantarell;font-size:14.6667px;font-weight:normal;=
text-align:left;background-color:rgb(255,255,255)">
Willtech</div>
<div style=3D"font-family:Cantarell;font-size:14.6667px;font-weight:normal;=
text-align:left;background-color:rgb(255,255,255)">
<a href=3D"http://www.willtech.com.au" style=3D"color:rgb(27,106,203)" rel=
=3D"noreferrer noreferrer noreferrer noreferrer noreferrer" target=3D"_blan=
k">www.willtech.com.au</a></div>
<div style=3D"font-family:Cantarell;font-size:14.6667px;font-weight:normal;=
text-align:left;background-color:rgb(255,255,255)">
<a href=3D"http://www.go-overt.com" style=3D"color:rgb(27,106,203)" rel=3D"=
noreferrer noreferrer noreferrer noreferrer noreferrer" target=3D"_blank">w=
ww.go-overt.com</a></div>
<div style=3D"font-family:Cantarell;font-size:14.6667px;font-weight:normal;=
text-align:left;background-color:rgb(255,255,255)">
and other projects</div>
<div style=3D"font-family:Cantarell;font-size:14.6667px;font-weight:normal;=
text-align:left;background-color:rgb(255,255,255)">
=C2=A0</div>
<div style=3D"font-family:Cantarell;font-size:14.6667px;font-weight:normal;=
text-align:left;background-color:rgb(255,255,255)">
<a href=3D"http://earn.com/willtech" rel=3D"noreferrer noreferrer noreferre=
r noreferrer noreferrer" target=3D"_blank">earn.com/willtech</a></div>
<div style=3D"font-family:Cantarell;font-size:14.6667px;font-weight:normal;=
text-align:left;background-color:rgb(255,255,255)">
<a href=3D"http://linkedin.com/in/damianwilliamson" rel=3D"noreferrer noref=
errer noreferrer noreferrer noreferrer" target=3D"_blank">linkedin.com/in/d=
amianwilliamson</a></div>
<div style=3D"font-family:Cantarell;font-size:14.6667px;font-weight:normal;=
text-align:left;background-color:rgb(255,255,255)">
<br>
</div>
<div style=3D"font-family:Cantarell;font-size:14.6667px;font-weight:normal;=
text-align:left;background-color:rgb(255,255,255)">
<br>
</div>
<div style=3D"font-family:Cantarell;font-size:14.6667px;font-weight:normal;=
text-align:left;background-color:rgb(255,255,255)">
m. 0487135719</div>
<div style=3D"font-family:Cantarell;font-size:14.6667px;font-weight:normal;=
text-align:left;background-color:rgb(255,255,255)">
f. +61261470192</div>
<div style=3D"font-family:Cantarell;font-size:14.6667px;font-weight:normal;=
text-align:left;background-color:rgb(255,255,255)">
<br>
</div>
<div style=3D"font-family:Cantarell;font-size:14.6667px;font-weight:normal;=
text-align:left;background-color:rgb(255,255,255)">
<br>
</div>
<span style=3D"font-family:Cantarell;font-size:14.6667px;font-weight:normal=
;text-align:left;background-color:rgb(255,255,255)">This email does not con=
stitute a general advice.
 Please disregard this email if misdelivered.</span>
<div>
<hr style=3D"display:inline-block;width:98%">
<div id=3D"m_3853911642162521674m_6630688057299329463m_-6828153514463161395=
m_7525661998923712526m_-1266539831211111536gmail-m_-5101036930417261306divR=
plyFwdMsg" dir=3D"ltr"><font style=3D"font-size:11pt" face=3D"Calibri, sans=
-serif" color=3D"#000000"><b>From:</b> bitcoin-dev &lt;<a href=3D"mailto:bi=
tcoin-dev-bounces@lists.linuxfoundation.org" rel=3D"noreferrer noreferrer n=
oreferrer noreferrer noreferrer" target=3D"_blank">bitcoin-dev-bounces@list=
s.linuxfoundation.org</a>&gt; on behalf of Lonero Foundation via bitcoin-de=
v &lt;<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" rel=3D"noref=
errer noreferrer noreferrer noreferrer noreferrer" target=3D"_blank">bitcoi=
n-dev@lists.linuxfoundation.org</a>&gt;<br>
<b>Sent:</b> Saturday, 6 March 2021 3:16 AM<br>
<b>To:</b> Devrandom &lt;<a href=3D"mailto:c1.devrandom@niftybox.net" rel=
=3D"noreferrer noreferrer noreferrer noreferrer noreferrer" target=3D"_blan=
k">c1.devrandom@niftybox.net</a>&gt;<br>
<b>Cc:</b> Bitcoin Protocol Discussion &lt;<a href=3D"mailto:bitcoin-dev@li=
sts.linuxfoundation.org" rel=3D"noreferrer noreferrer noreferrer noreferrer=
 noreferrer" target=3D"_blank">bitcoin-dev@lists.linuxfoundation.org</a>&gt=
;<br>
<b>Subject:</b> Re: [bitcoin-dev] BIP Proposal: Consensus (hard fork) PoST =
Datastore for Energy Efficient Mining</font>
<div>=C2=A0</div>
</div>
<div>
<div dir=3D"auto">Also in regards to my other email, I forgot to iterate th=
at my cryptography proposal helps behind the efficiency category but also t=
ackles problems such as NP-Completeness or Halting which is something the B=
TC network could be vulnerable to
 in the future. For sake of simplicity, I do want to do this BIP because it=
 tackles lots of the issues in regards to this manner and can provide usefu=
l insight to the community. If things such as bigger block height have been=
 proposed as hard forks, I feel
 at the very least an upgrade regarding the hashing algorithm and cryptogra=
phy does at least warrant some discussion. Anyways I hope I can send you my=
 BIP, just let me know on the preferred format?
<div dir=3D"auto"><br>
</div>
<div dir=3D"auto">Best regards, Andrew</div>
</div>
<br>
<div>
<div dir=3D"ltr">On Fri, Mar 5, 2021, 10:12 AM Lonero Foundation &lt;<a hre=
f=3D"mailto:loneroassociation@gmail.com" rel=3D"noreferrer noreferrer noref=
errer noreferrer noreferrer" target=3D"_blank">loneroassociation@gmail.com<=
/a>&gt; wrote:<br>
</div>
<blockquote style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204=
,204,204);padding-left:1ex">
<div dir=3D"auto">Hi, this isn&#39;t about the energy efficient argument in=
 regards to renewables or mining devices but a better cryptography layer to=
 get the most out of your hashing for validation. I do understand the arbit=
rariness of it, but do want to still propose
 a document. Do I use the Media Wiki format on GitHub and just attach it as=
 my proposal?
<div dir=3D"auto"><br>
</div>
<div dir=3D"auto">Best regards, Andrew</div>
</div>
<br>
<div>
<div dir=3D"ltr">On Fri, Mar 5, 2021, 10:07 AM Devrandom &lt;<a href=3D"mai=
lto:c1.devrandom@niftybox.net" rel=3D"noreferrer noreferrer noreferrer nore=
ferrer noreferrer noreferrer" target=3D"_blank">c1.devrandom@niftybox.net</=
a>&gt; wrote:<br>
</div>
<blockquote style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204=
,204,204);padding-left:1ex">
<div dir=3D"auto">
<div dir=3D"ltr">
<div>Hi Ryan and Andrew,<br>
</div>
<br>
<div>
<div dir=3D"ltr">On Fri, Mar 5, 2021 at 5:42 AM Ryan Grant via bitcoin-dev =
&lt;<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" rel=3D"norefer=
rer noreferrer noreferrer noreferrer noreferrer noreferrer noreferrer noref=
errer" target=3D"_blank">bitcoin-dev@lists.linuxfoundation.org</a>&gt; wrot=
e:<br>
</div>
<blockquote style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204=
,204,204);padding-left:1ex">
<br>
=C2=A0 <a href=3D"https://www.truthcoin.info/blog/pow-cheapest/" rel=3D"nor=
eferrer noreferrer noreferrer noreferrer noreferrer noreferrer noreferrer n=
oreferrer noreferrer" target=3D"_blank">
https://www.truthcoin.info/blog/pow-cheapest/</a><br>
=C2=A0 =C2=A0 &quot;Nothing is Cheaper than Proof of Work&quot;<br>
=C2=A0 =C2=A0 on | 04 Aug 2015<br>
<br>
</blockquote>
<div><br>
</div>
<div>Just to belabor this a bit, the paper demonstrates that the mining mar=
ket will tend to expend resources equivalent to miner reward.=C2=A0 It does=
 not prove that mining work has to expend *energy* as a primary cost.<br>
</div>
<div><br>
</div>
<div>Some might argue that energy expenditure has negative externalities an=
d that we should move to other resources.=C2=A0 I would argue that the nega=
tive externalities will go away soon because of the move to renewables, so =
the point is likely moot.=C2=A0</div>
<div><br>
</div>
</div>
</div>
</div>
</blockquote>
</div>
</blockquote>
</div>
</div>
</div>
</div>

_______________________________________________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" rel=3D"noreferrer =
noreferrer noreferrer noreferrer noreferrer" target=3D"_blank">bitcoin-dev@=
lists.linuxfoundation.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer noreferrer noreferrer noreferrer noreferrer noreferrer" t=
arget=3D"_blank">https://lists.linuxfoundation.org/mailman/listinfo/bitcoin=
-dev</a><br>
</blockquote></div>
</blockquote></div>
</blockquote></div>
</blockquote></div>

--0000000000004ddf5a05bd8a6ea3--