From: Luke Kenneth Casson Leighton <lkcl@lkcl•net>
To: ZmnSCPxj <ZmnSCPxj@protonmail•com>
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Libre/Open blockchain / cryptographic ASICs
Date: Wed, 3 Feb 2021 14:07:24 +0000 [thread overview]
Message-ID: <CAPweEDxRUaGDrezZqdM9dm9QrbQtxF_JZND84SQfgX_yQUuvLA@mail.gmail.com> (raw)
In-Reply-To: <S5xSo0WU5O0xwb5Ot7jF8L011HUGf1oSpJSxtB93NY8qDZDwtCcNh9LSILMaZvT4uBh43jl638H7_bCz1WtSde34i0LnsNsXOyoJjuN5RIw=@protonmail.com>
[-- Attachment #1: Type: text/plain, Size: 1178 bytes --]
On Wednesday, February 3, 2021, ZmnSCPxj <ZmnSCPxj@protonmail•com> wrote:
> Good morning again Luke,
:)
> If you mean miner power usage, then power efficiency will not reduce
energy consumption.
> Thus, any rational miner will just pack more miners in the same number of
watts rather than reduce their watt consumption.
yes, of course. the same non-consumer-computing-intuitive logic applies to
purchasing decisions for beowulf clusters.
> Thus, increasing power efficiency for mining does not reduce the amount
of actual energy that will be consumed by Bitcoin mining.
arse.
and if everybody does that, then no matter the performance/watt nobody
"wins". in fact a case could be made that everybody "loses".
my biggest concern here is that the inherent "arms race" results in very
few players being able to create bitcoin mining ASICs *at all*.
i mentioned earlier that geometry costs are an exponential scale. 3nm must
be somewhere around USD 16 million for production masks.
if there are only a few players that leaves the entirety of bitcoin open to
hardware backdoors.
l.
--
---
crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68
[-- Attachment #2: Type: text/html, Size: 1458 bytes --]
prev parent reply other threads:[~2021-02-03 14:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-25 18:00 Luke Kenneth Casson Leighton
2021-01-26 10:47 ` Pavol Rusnak
2021-02-03 2:06 ` ZmnSCPxj
2021-02-03 13:24 ` Luke Kenneth Casson Leighton
2021-02-11 8:20 ` ZmnSCPxj
2021-02-13 6:10 ` ZmnSCPxj
2021-02-13 9:29 ` Luke Kenneth Casson Leighton
[not found] ` <CAPweEDymve0zRaqN9yEGHyOeuaSLEYWQ0K2h6usWbXiV=HkOzA@mail.gmail.com>
2021-02-13 14:59 ` Bryan Bishop
2021-02-13 16:44 ` Luke Kenneth Casson Leighton
2021-02-13 17:19 ` Luke Kenneth Casson Leighton
2021-02-14 0:27 ` ZmnSCPxj
2021-02-03 3:17 ` ZmnSCPxj
2021-02-03 14:07 ` Luke Kenneth Casson Leighton [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAPweEDxRUaGDrezZqdM9dm9QrbQtxF_JZND84SQfgX_yQUuvLA@mail.gmail.com \
--to=lkcl@lkcl$(echo .)net \
--cc=ZmnSCPxj@protonmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox