path: root/0f/c9267327584e4986d13e5fe2f026a1305bd67d

Return-Path: <keagan.mcclelland@gmail.com>
Received: from smtp4.osuosl.org (smtp4.osuosl.org [IPv6:2605:bc80:3010::137])
 by lists.linuxfoundation.org (Postfix) with ESMTP id 4E3CFC0001
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Tue, 18 May 2021 16:47:46 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by smtp4.osuosl.org (Postfix) with ESMTP id 2824840E43
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Tue, 18 May 2021 16:47:46 +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,
 HK_SCAM_S7=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001,
 SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: smtp4.osuosl.org (amavisd-new);
 dkim=pass (2048-bit key) header.d=gmail.com
Received: from smtp4.osuosl.org ([127.0.0.1])
 by localhost (smtp4.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id vnZQg31S2sm3
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Tue, 18 May 2021 16:47:44 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.8.0
Received: from mail-wr1-x432.google.com (mail-wr1-x432.google.com
 [IPv6:2a00:1450:4864:20::432])
 by smtp4.osuosl.org (Postfix) with ESMTPS id C0D81406AF
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Tue, 18 May 2021 16:47:43 +0000 (UTC)
Received: by mail-wr1-x432.google.com with SMTP id z17so10953396wrq.7
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Tue, 18 May 2021 09:47:43 -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=jezg/vaZ98Q5bH+aJxFh7QiFLRSgJsPczvb/Z5cQb3A=;
 b=V3QNYaSmxmBCNas2zNepNm29mAye7N0pOPCNWB6uTO3UwX6QPEpUTC+U2lT1S7HOFY
 8FLDsglgwGY0g8ci3o4L+HYSVBhNeMNkQqfLk2yIALnNTXhtU5+DxYQmfnvlmxzAjVmf
 j0H126la+6q7H+15IBK+dsKqNpWezYGkoGqQpKaPmQEh5JxjFMHzCxA6bSCfpwZ12y5q
 j6pdvoy8U2ZW0doY83pNuHUGc4RRwkFnzNBoDenCeOp5hNQkLRdrQcEciopBGrN6XJGl
 BBXrFs53U0lkQ6Uew0lia5XZEom21ep9gQooXAV0v5hdF2spc+uio8DsgZVhaWy8l9SI
 BZkg==
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=jezg/vaZ98Q5bH+aJxFh7QiFLRSgJsPczvb/Z5cQb3A=;
 b=UKDS/3P3AMfbMV9WvYQUQMbhi/kRLwt/9pBFNHGl3UfN6qvx/HlsgD3btJMYuqxS+c
 3rGMKT7b8beEm6RM8AJPtHr2Vd3CWm4PAoi1uMipV7oiu/fcTEoIenxQ8rpazuJUN1qn
 OYFkAlJmSYlYoh8+EkeRTdwvS0DJwiMkpqSnVkPKgqwJ91gFWenBU623ySbaB0cy5DtQ
 wJWNDAEzIIp97nsI7zt6HdlwRtr7lPPpOl42ds3NBsQ/6Q2OjEs7SUndvOtSomGdsodg
 sMkx9+EzvPs8SH48FiDgrYmxzTByrpykpPQxiAVpuCXihxS9Ts7hYpFuRGwkOclJxUSx
 Q8Xg==
X-Gm-Message-State: AOAM533L4eUrlqsdwJfaCOUahTIiKBs4URsnGtPsLazOnJ59IUo1F0jh
 1GplsipDgWhNDLUUSE5A/Oo3tkANS7wupgGhqpo=
X-Google-Smtp-Source: ABdhPJzH9GTfUK6Dc9cCIbeYmvOLI3jz0iX2aLlHw16PXHWJBBmntuwhaiCxQ4y55f9wzPM4DJUe6GmIdPEPWZCDbDc=
X-Received: by 2002:a5d:4d0b:: with SMTP id z11mr8486309wrt.164.1621356461899; 
 Tue, 18 May 2021 09:47:41 -0700 (PDT)
MIME-Version: 1.0
References: <CAGFmrSac+Ej1a6da8GcPK1pB_kgowtQk5roaDCVsL9t1zgwEFA@mail.gmail.com>
 <CALeFGL3U2yb2WVz4rwcBqO25kd0B7NcgrN4iMjDyackrTTegpw@mail.gmail.com>
 <ZFVpoVGcwTTpDDlAXLn8cCwic0l40b3DmE_UoKIv4IvmFDDX9W2F1sRHYwido1X7OK0fX1QAx5J8I5DokM4pcIKziNAgAwc6emrHulfbRE8=@protonmail.com>
 <CANPykMoM4+3svpUNQBwa8xrsKnEv48FVT1fu0+wpnTB4PXkg4g@mail.gmail.com>
In-Reply-To: <CANPykMoM4+3svpUNQBwa8xrsKnEv48FVT1fu0+wpnTB4PXkg4g@mail.gmail.com>
From: Keagan McClelland <keagan.mcclelland@gmail.com>
Date: Tue, 18 May 2021 10:47:29 -0600
Message-ID: <CALeFGL3SJw94DOgOHjwTSM+6Vc74tTuCHFu1QjDM+FjYSGxGNA@mail.gmail.com>
To: Claus Ehrenberg <aubergemediale@gmail.com>, 
 Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary="000000000000f7444c05c29d774f"
X-Mailman-Approved-At: Tue, 18 May 2021 20:55:08 +0000
Subject: Re: [bitcoin-dev] Proposal: Low Energy Bitcoin PoW
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: Tue, 18 May 2021 16:47:46 -0000

--000000000000f7444c05c29d774f
Content-Type: text/plain; charset="UTF-8"

>One needs a cost/benefit analysis, not just an account of the cost. For
example, if PoW could do calculations that are otherwise useful (maybe
solve a queue of standardized math-jobs, such as climate simulations) there
would be more benefit, or, let's say the data storage in proof-of-space is
useful.

Any discussion on whether Proof of Work is suitable for the task needs to
recognize that the "waste" is what creates the security. If you manage to
make the proof of work useful for tasks external to the protocol, you
reintroduce the "nothing at stake" problem in a roundabout way. Useful
computation is something people will pay for. If they pay for it, miners
can be compensated in such a way that choosing to mine one of the
Not-The-Heaviest-Chain's becomes costless. This erodes the security of the
network substantially. It is not a matter of coming up with the "right"
kind of useful computation that is not subject to these problems. These
problems are a natural consequence of it being useful outside the protocol
*at all*.

Keagan

On Tue, May 18, 2021 at 8:24 AM Claus Ehrenberg via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:

> > Ultimately all currency security derives from energy consumption.
> > Everything eventually resolves down to proof-of-work.
> This is ideology. Yes, without energy and work, not many things happen.
> But the amounts of energy and work to achieve a goal vary widely. Detailed
> analysis comparing one alternative with the other in depth  is required.
> And I would not look for order-of-magnitude improvements, 25% better is
> also a big deal, if discovered.
>
> > * Proof-of-space simply moves the work to the construction of more
> storage devices.
> One needs a cost/benefit analysis, not just an account of the cost. For
> example, if PoW could do calculations that are otherwise useful (maybe
> solve a queue of standardized math-jobs, such as climate simulations) there
> would be more benefit, or, let's say the data storage in proof-of-space is
> useful.
>
> > * Proof-of-stake simply moves the work to stake-grinding attacks.
> Simply not true, there are PoS implementations that are immune to
> stake-grinding attacks, and even where not, the possible amount of
> computations is limited compared to PoW
>
> > * The optical proof-of-work simply moves the work to the construction of
> more miners.
> The idea was to shift from energy to cap-ex. We can get a
> financial penalty for misbehavior from three sources:
> - cost of energy/labor (PoW)
> - cost of capital (PoS)
> - cost of cap-ex
> There might be a better mix than PoW only. I have written code for mixed
> PoW/PoS systems and it works. Adding more cap-ex to the mix can make sense,
> but the environmental impact needs to be analyzed, it could also make it
> worse than just the use of electricity. At least electricity as such does
> not leave waste behind. Mining in orbit with solar power would be totally
> acceptable.
>
> > At least, proof-of-work is honest about its consumption of resources.
> Agreed, but we can't be satisfied with that. If we try hard enough we can
> do better.
>
> Cheers
> Claus
>
> On Tue, May 18, 2021 at 8:47 AM ZmnSCPxj via bitcoin-dev <
> bitcoin-dev@lists.linuxfoundation.org> wrote:
>
>>
>> > A few things jump out at me as I read this proposal
>> >
>> > First, deriving the hardness from capex as opposed to opex switches the
>> privilege from those who have cheap electricity to those who have access to
>> chip manufacturers/foundries. While this is similarly the case for Bitcoin
>> ASICS today, the longevity of the PoW algorithm has led to a better
>> distribution of knowledge and capital goods required to create ASICS. The
>> creation of a new PoW of any kind, hurts this dimension of decentralization
>> as we would have to start over from scratch on the best way to build,
>> distribute, and operate these new pieces of hardware at scale. While I have
>> not combed over the PoW proposed here in fine detail, the more complicated
>> the algorithm is, the more it privileges those with specific knowledge
>> about it and the manufacturing process.
>> >
>> > The competitive nature of Bitcoin mining is such that miners will be
>> willing to spend up to their expected mining reward in their operating
>> costs to continue to mine. Let's suppose that this new PoW was adopted,
>> miners will continue to buy these chips in ever increasing quantities,
>> turning the aforementioned CAPEX into a de facto OPEX. This has a few
>> consequences. First it just pushes the energy consumption upstream to the
>> chip manufacturing process, rather than eliminating it. And it may trade
>> some marginal amount of the energy consumption for the set of resources it
>> takes to educate and create chip manufacturers. The only way to avoid that
>> cost being funneled back into more energy consumption is to make the
>> barrier to understanding of the manufacturing process sufficiently
>> difficult so as to limit the proliferation of these chips. Again, this
>> privileges the chip manufacturers as well as those with close access to the
>> chip manufacturers.
>> >
>> > As far as I can tell, the only thing this proposal actually does is
>> create a very lucrative business model for those who sell this variety of
>> chips. Any other effects of it are transient, and in all likelihood the
>> transient effects create serious centralization pressure.
>> >
>> > At the end of the day, the energy consumption is foundational to the
>> system. The only way to do away with authorities, is to require
>> competition. This competition will employ ever more resources until it is
>> unprofitable to do so. At the base of all resources of society is energy.
>> You get high energy expenditure, or a privileged class of bitcoin
>> administrators: pick one. I suspect you'll find the vast majority of
>> Bitcoin users to be in the camp of the energy expenditure, since if we pick
>> the latter, we might as well just pack it in and give up on the Bitcoin
>> experiment.
>>
>>
>> Keagan is quite correct.
>> Ultimately all currency security derives from energy consumption.
>> Everything eventually resolves down to proof-of-work.
>>
>> * Proof-of-space simply moves the work to the construction of more
>> storage devices.
>> * Proof-of-stake simply moves the work to stake-grinding attacks.
>> * The optical proof-of-work simply moves the work to the construction of
>> more miners.
>> * Even government-enforced fiat is ultimately proof-of-work, as the
>> operation and continued existence of any government is work.
>>
>> It is far better to move towards a more *direct* proof-of-work, than to
>> add more complexity and come up with something that is just proof-of-work,
>> but with the work moved off to somewhere else and with additional moving
>> parts that can be jammed or hacked into.
>>
>> When considering any new proof-of-foo, it is best to consider all effects
>> until you reach the base physics of the arrow of time, at which point you
>> will realize it is ultimately just another proof-of-work anyway.
>>
>> At least, proof-of-work is honest about its consumption of resources.
>>
>>
>> Regards,
>> ZmnSCPxj
>> _______________________________________________
>> bitcoin-dev mailing list
>> bitcoin-dev@lists.linuxfoundation.org
>> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>

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

<div dir=3D"ltr"><div>&gt;One needs a cost/benefit analysis, not just an ac=
count of the cost. For example, if PoW could do calculations that are other=
wise useful (maybe solve a queue of standardized math-jobs, such as climate=
 simulations) there would be more benefit, or, let&#39;s say the data stora=
ge in proof-of-space is useful.</div><div><br></div>Any discussion on wheth=
er Proof of Work is suitable for the task needs to recognize that the &quot=
;waste&quot; is what creates the security. If you manage to make the proof =
of work useful for tasks external to the protocol, you reintroduce the &quo=
t;nothing at stake&quot; problem in a roundabout way. Useful computation is=
 something people will pay for. If they pay for it, miners can be compensat=
ed in such a way that choosing to mine one of the Not-The-Heaviest-Chain&#3=
9;s becomes costless. This erodes the security of the network substantially=
. It is not a matter of coming up with the &quot;right&quot; kind of useful=
 computation that is not subject to these problems. These problems are a na=
tural consequence of it being useful outside the protocol *at all*.<div><br=
></div><div>Keagan</div></div><br><div class=3D"gmail_quote"><div dir=3D"lt=
r" class=3D"gmail_attr">On Tue, May 18, 2021 at 8:24 AM Claus Ehrenberg via=
 bitcoin-dev &lt;<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">b=
itcoin-dev@lists.linuxfoundation.org</a>&gt; wrote:<br></div><blockquote cl=
ass=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid=
 rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr">&gt; Ultimately all cu=
rrency security derives from energy consumption.<br>&gt; Everything eventua=
lly resolves down to proof-of-work.<br><div>This is ideology. Yes, without =
energy and work, not many things happen. But the amounts of energy and work=
 to achieve a goal vary widely. Detailed analysis comparing one alternative=
 with the other in depth=C2=A0 is required. And I would not look for order-=
of-magnitude improvements, 25% better is also a big deal, if discovered.</d=
iv><div><br></div><div>&gt; * Proof-of-space simply moves the work to the c=
onstruction of more storage devices.</div><div>One needs a cost/benefit ana=
lysis, not just an account of the cost. For example, if PoW could do calcul=
ations that are otherwise useful (maybe solve a queue of standardized math-=
jobs, such as climate simulations) there would be more benefit, or, let&#39=
;s say the data storage in proof-of-space is useful.</div><div><br></div><d=
iv>&gt; * Proof-of-stake simply moves the work to stake-grinding attacks.<b=
r></div><div>Simply not true, there are PoS implementations that are immune=
=C2=A0to stake-grinding attacks, and even where not, the possible amount of=
 computations is limited compared to PoW</div><div><br></div><div>&gt; * Th=
e optical proof-of-work simply moves the work to the construction of more m=
iners.<br></div><div>The idea was to shift from energy to cap-ex. We can ge=
t a financial=C2=A0penalty for misbehavior from three sources:<br>- cost of=
 energy/labor (PoW)</div><div>- cost of capital (PoS)</div><div>- cost of c=
ap-ex</div><div>There might be a better mix than PoW only. I have written c=
ode for mixed PoW/PoS systems and it works. Adding more cap-ex to the mix c=
an make sense, but the environmental impact needs to be analyzed, it could =
also make it worse than just the use of electricity. At least electricity a=
s such does not leave waste behind. Mining in orbit with solar power would =
be totally acceptable.</div><div><br></div><div>&gt; At least, proof-of-wor=
k is honest about its consumption of resources.<br></div><div>Agreed, but w=
e can&#39;t be satisfied with that. If we try hard enough we can do better.=
</div><div><br></div><div>Cheers</div><div>Claus</div></div><br><div class=
=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Tue, May 18, 2021=
 at 8:47 AM ZmnSCPxj via bitcoin-dev &lt;<a href=3D"mailto:bitcoin-dev@list=
s.linuxfoundation.org" target=3D"_blank">bitcoin-dev@lists.linuxfoundation.=
org</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"marg=
in:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1e=
x"><br>
&gt; A few things jump out at me as I read this proposal<br>
&gt;<br>
&gt; First, deriving the hardness from capex as opposed to opex switches th=
e privilege from those who have cheap electricity to those who have access =
to chip manufacturers/foundries. While this is similarly the case for Bitco=
in ASICS today, the longevity of the PoW algorithm has led to a better dist=
ribution of knowledge and capital goods required to create ASICS. The creat=
ion of a new PoW of any kind, hurts this dimension of decentralization as w=
e would have to start over from scratch on the best way to build, distribut=
e, and operate these new pieces of hardware at scale. While I have not comb=
ed over the PoW proposed here in fine detail, the more complicated the algo=
rithm is, the more it privileges those with specific knowledge about it and=
 the manufacturing process.<br>
&gt;<br>
&gt; The competitive nature of Bitcoin mining is such that miners will be w=
illing to spend up to their expected mining reward in their operating costs=
 to continue to mine. Let&#39;s suppose that this new PoW was adopted, mine=
rs will continue to buy these chips in ever increasing quantities, turning =
the aforementioned CAPEX into a de facto OPEX. This has a few consequences.=
 First it just pushes the energy consumption upstream to the chip manufactu=
ring process, rather than eliminating it. And it may trade some marginal am=
ount of the energy consumption for the set of resources it takes to educate=
 and create chip manufacturers. The only way to avoid that cost being funne=
led back into more energy consumption is to make the barrier to understandi=
ng of the manufacturing process sufficiently difficult so as to limit the p=
roliferation of these chips. Again, this privileges the chip manufacturers =
as well as those with close access to the chip manufacturers.<br>
&gt;<br>
&gt; As far as I can tell, the only thing this proposal actually does is cr=
eate a very lucrative business model for those who sell this variety of chi=
ps. Any other effects of it are transient, and in all likelihood the transi=
ent effects create serious centralization pressure.<br>
&gt;<br>
&gt; At the end of the day, the energy consumption is foundational to the s=
ystem. The only way to do away with authorities, is to require competition.=
 This competition will employ ever more resources until it is unprofitable =
to do so. At the base of all resources of society is energy. You get high e=
nergy expenditure, or a privileged class of bitcoin administrators: pick on=
e. I suspect you&#39;ll find the vast majority of Bitcoin users to be in th=
e camp of the energy expenditure, since if we pick the latter, we might as =
well just pack it in and give up on the Bitcoin experiment.<br>
<br>
<br>
Keagan is quite correct.<br>
Ultimately all currency security derives from energy consumption.<br>
Everything eventually resolves down to proof-of-work.<br>
<br>
* Proof-of-space simply moves the work to the construction of more storage =
devices.<br>
* Proof-of-stake simply moves the work to stake-grinding attacks.<br>
* The optical proof-of-work simply moves the work to the construction of mo=
re miners.<br>
* Even government-enforced fiat is ultimately proof-of-work, as the operati=
on and continued existence of any government is work.<br>
<br>
It is far better to move towards a more *direct* proof-of-work, than to add=
 more complexity and come up with something that is just proof-of-work, but=
 with the work moved off to somewhere else and with additional moving parts=
 that can be jammed or hacked into.<br>
<br>
When considering any new proof-of-foo, it is best to consider all effects u=
ntil you reach the base physics of the arrow of time, at which point you wi=
ll realize it is ultimately just another proof-of-work anyway.<br>
<br>
At least, proof-of-work is honest about its consumption of resources.<br>
<br>
<br>
Regards,<br>
ZmnSCPxj<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>
_______________________________________________<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>

--000000000000f7444c05c29d774f--