summaryrefslogtreecommitdiff
path: root/6c/dfd457397411d6a9333031be669c777e7219fc
blob: 3cd982c04db0a8dbe8489da9185d20afaaaa648f (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
Return-Path: <eric@ericmartindale.com>
Received: from smtp2.osuosl.org (smtp2.osuosl.org [IPv6:2605:bc80:3010::133])
 by lists.linuxfoundation.org (Postfix) with ESMTP id 735A9C0001
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Sat,  8 May 2021 13:44:41 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by smtp2.osuosl.org (Postfix) with ESMTP id 55C6140132
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Sat,  8 May 2021 13:44:41 +0000 (UTC)
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -1.789
X-Spam-Level: 
X-Spam-Status: No, score=-1.789 tagged_above=-999 required=5
 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001,
 SPF_PASS=-0.001, T_DKIM_INVALID=0.01, UNPARSEABLE_RELAY=0.001]
 autolearn=no autolearn_force=no
Authentication-Results: smtp2.osuosl.org (amavisd-new); dkim=neutral
 reason="invalid (public key: not available)"
 header.d=ericmartindale.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 3v5OnYMRxR4E
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Sat,  8 May 2021 13:44:39 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.8.0
Received: from mail.verit.ae (mail.verit.ae [213.239.212.102])
 by smtp2.osuosl.org (Postfix) with ESMTPS id 9D5F240003
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Sat,  8 May 2021 13:44:39 +0000 (UTC)
Received: from authenticated-user (mail.verit.ae [213.239.212.102])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (No client certificate requested)
 by mail.verit.ae (Postfix) with ESMTPSA id EF7D5100B27
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Sat,  8 May 2021 15:44:35 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=ericmartindale.com;
 s=mail; t=1620481476;
 bh=8dK2t9L1+aoNZwQpmG26eqgqKD+E5UDztHDfetu24ac=;
 h=References:In-Reply-To:From:Date:Subject:To:From;
 b=XWZ0ZOkSAKnInebV6kMTHpxxlb9hUMlVzBYZZG6PIp8FVph5NIvk4CsQ3ff2kTYin
 C2JcWMhO5pFlkiMW4qBJrgPBSh8wFkCUW03NkNciwGVr8vXnyGT2tjTfwdy8qtWkHt
 vrDBJYms73eXeJ1x96agVEMCLQwblrkLsbAokW+RN5TxdSaOFgufyyDGgZX4J1sNg3
 ETodkbQndEr8qEP+KVMvgR2UcLvSrNm5ZYcs+2f22NfyfbJ2fgQWIPhTvE2kqfsffY
 8e3kLo/W4eiagbFqhRVi6aD49uzDD7QzUK3g32KVn0R3ED2bJ5cYuPhS42PLHkK5Y8
 FqJCBVUmClzXQ==
Received: from authenticated-user (mail.verit.ae [213.239.212.102])
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Sat, 08 May 2021 06:44:35 -0700 (PDT)
X-Gm-Message-State: AOAM533kAwbOS2Pz7c5UqRits97vixh/pb3els1bEOuYmB1VxnSjWwX6
 V+8lltq0QIzb/RuqrHsQYF1bu8xiZr3bnIfrdDA=
X-Google-Smtp-Source: ABdhPJxYboRD2n0TMf1nBc5/JBDs+JkL1GCHq8D/QYm2a1Z3GlU7js37XFixWT1IUZrR8CPdvHdCleMnljwdqpJk/Gs=
X-Received: by 2002:a17:906:3111:: with SMTP id
 17mr15398581ejx.403.1620481475460; 
 Sat, 08 May 2021 06:44:35 -0700 (PDT)
MIME-Version: 1.0
References: <6do5xN2g5LPnFeM55iJ-4C4MyXOu_KeXxy68Xt4dJQMhi3LJ8ZrLICmEUlh8JGfDmsDG12m1JDAh0e0huwK_MlyKpdfn22ru3zsm7lYLfBo=@protonmail.com>
In-Reply-To: <6do5xN2g5LPnFeM55iJ-4C4MyXOu_KeXxy68Xt4dJQMhi3LJ8ZrLICmEUlh8JGfDmsDG12m1JDAh0e0huwK_MlyKpdfn22ru3zsm7lYLfBo=@protonmail.com>
From: Eric Martindale <eric@ericmartindale.com>
Date: Sat, 8 May 2021 09:44:24 -0400
X-Gmail-Original-Message-ID: <CAAf19Wq4Bbte5aKJKZVyvesWQ-=HVmH17rz6rE=w8=7sN7rgmw@mail.gmail.com>
Message-ID: <CAAf19Wq4Bbte5aKJKZVyvesWQ-=HVmH17rz6rE=w8=7sN7rgmw@mail.gmail.com>
To: SatoshiSingh <SatoshiSingh@protonmail.com>, 
 Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary="000000000000b5c44805c1d1bef4"
X-Mailman-Approved-At: Sat, 08 May 2021 13:46:10 +0000
Subject: Re: [bitcoin-dev] Opinion on proof of stake in future
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, 08 May 2021 13:44:41 -0000

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

Mr. Singh,

Proof of Stake is only resilient to =E2=85=93 of the network demonstrating =
a
Byzantine Fault, whilst Proof of Work is resilient up to the =C2=BD thresho=
ld.
You can explore prior research here:
https://download.wpsoftware.net/bitcoin/pos.pdf

Independent of the security thresholds, Proof of Stake requires other
trade-offs which are incompatible with Bitcoin's objective (to be a
trustless digital cash) =E2=80=94 specifically the famous "security vs. liv=
eness"
guarantee.  Digital cash is not useful if it must be globally halted to
ensure its security, and Proof of Work squarely addresses this concern.

Above and beyond any security consideration, Proof of Stake incentivizes
the accumulation of wealth within a small set of actors, which is
undesirable for the long-term health of any such network.  If we are to
free humanity from the tyranny of the State, we must do so by protecting
the rights of every individual to hold and preserve their own value,
without trusting any third party.  Entrusting the health of the network to
the "economic elite" is the paramount evil with respect to Bitcoin's
objectives, nevermind that Proof of Work relies on energy expenditure to
provide its security.

Sincerely,

Eric Martindale, relentless maker.
Founder & CEO, Fabric, Inc. <https://fabric.fm>
+1 (919) 374-2020


On Fri, May 7, 2021 at 6:50 PM SatoshiSingh via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:

> Hello list,
>
> I am a lurker here and like many of you I worry about the energy usage of
> bitcoin mining. I understand a lot mining happens with renewable resource=
s
> but the impact is still high.
>
> I want to get your opinion on implementing proof of stake for bitcoin
> mining in future. For now, proof of stake is still untested and not battl=
e
> tested like proof of work. Though someday it will be.
>
> In the following years we'll be seeing proof of stake being implemented.
> Smaller networks can test PoS which is a luxury bitcoin can't afford.
> Here's how I see this the possibilities:
>
> 1 - Proof of stake isn't a good enough security mechanism
> 2 - Proof of state is a good security mechanism and works as intended
>
> IF PoS turns out to be good after battle testing, would you consider
> implementing it for Bitcoin? I understand this would invoke a lot of
> controversies and a hard fork that no one likes. But its important enough
> to consider a hard fork. What are your opinions provided PoS does work?
>
> Love from India.
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>

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

<div dir=3D"ltr">Mr. Singh,<br><br>Proof of Stake is only resilient to=C2=
=A0=E2=85=93 of the network demonstrating a Byzantine Fault, whilst Proof o=
f Work is resilient up to the=C2=A0=C2=BD threshold.=C2=A0 You can explore =
prior research here:=C2=A0<a href=3D"https://download.wpsoftware.net/bitcoi=
n/pos.pdf" target=3D"_blank">https://download.wpsoftware.net/bitcoin/pos.pd=
f</a><br><br>Independent of the security thresholds, Proof of Stake require=
s other trade-offs which are incompatible with Bitcoin&#39;s objective (to =
be a trustless digital cash) =E2=80=94 specifically the famous &quot;securi=
ty vs. liveness&quot; guarantee.=C2=A0 Digital cash is not useful if it mus=
t be globally halted to ensure its security, and Proof of Work squarely add=
resses this concern.<br><br>Above and beyond any security consideration, Pr=
oof of Stake incentivizes the accumulation of wealth within a small set of =
actors, which is undesirable for the long-term health of any such network.=
=C2=A0 If we are to free humanity from the tyranny of the State, we must do=
 so by protecting the rights of every individual to hold and preserve their=
 own value, without trusting any third party.=C2=A0 Entrusting the health o=
f the network to the &quot;economic elite&quot; is the paramount evil with =
respect to Bitcoin&#39;s objectives, nevermind that Proof of Work relies on=
 energy expenditure to provide its security.<br><br>Sincerely,<br><br><div>=
<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;He=
lvetica Neue&quot;,Helvetica,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" target=3D"_blank">Fabric, Inc.</a></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">+1 (919) 374-2020</div></div></div></div></di=
v></div><br></div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" cla=
ss=3D"gmail_attr">On Fri, May 7, 2021 at 6:50 PM SatoshiSingh via bitcoin-d=
ev &lt;<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_=
blank">bitcoin-dev@lists.linuxfoundation.org</a>&gt; wrote:<br></div><block=
quote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1=
px solid rgb(204,204,204);padding-left:1ex">Hello list,<br>
<br>
I am a lurker here and like many of you I worry about the energy usage of b=
itcoin mining. I understand a lot mining happens with renewable resources b=
ut the impact is still high.<br>
<br>
I want to get your opinion on implementing proof of stake for bitcoin minin=
g in future. For now, proof of stake is still untested and not battle teste=
d like proof of work. Though someday it will be.<br>
<br>
In the following years we&#39;ll be seeing proof of stake being implemented=
. Smaller networks can test PoS which is a luxury bitcoin can&#39;t afford.=
 Here&#39;s how I see this the possibilities:<br>
<br>
1 - Proof of stake isn&#39;t a good enough security mechanism<br>
2 - Proof of state is a good security mechanism and works as intended<br>
<br>
IF PoS turns out to be good after battle testing, would you consider implem=
enting it for Bitcoin? I understand this would invoke a lot of controversie=
s and a hard fork that no one likes. But its important enough to consider a=
 hard fork. What are your opinions provided PoS does work?<br>
<br>
Love from India.<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>

--000000000000b5c44805c1d1bef4--