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
|
Return-Path: <jlrubin@mit.edu>
Received: from smtp2.osuosl.org (smtp2.osuosl.org [140.211.166.133])
by lists.linuxfoundation.org (Postfix) with ESMTP id 6458BC0001
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 10 May 2021 21:51:41 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by smtp2.osuosl.org (Postfix) with ESMTP id 53E8D403A4
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 10 May 2021 21:51:41 +0000 (UTC)
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3,
SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 HnyYuFzaEM5L
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 10 May 2021 21:51:40 +0000 (UTC)
X-Greylist: domain auto-whitelisted by SQLgrey-1.8.0
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11])
by smtp2.osuosl.org (Postfix) with ESMTPS id 795DE402C9
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 10 May 2021 21:51:40 +0000 (UTC)
Received: from mail-il1-f176.google.com (mail-il1-f176.google.com
[209.85.166.176]) (authenticated bits=0)
(User authenticated as jlrubin@ATHENA.MIT.EDU)
by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 14ALpcIR010398
(version=TLSv1/SSLv3 cipher=AES128-GCM-SHA256 bits=128 verify=NOT)
for <bitcoin-dev@lists.linuxfoundation.org>; Mon, 10 May 2021 17:51:38 -0400
Received: by mail-il1-f176.google.com with SMTP id l19so15389563ilk.13
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 10 May 2021 14:51:38 -0700 (PDT)
X-Gm-Message-State: AOAM530hGBCu+TZqh6twlsFBIq8rpksA669MSbJgzWFevAzX+8yiT4F3
MHxxAPFyuX3sWqTkTgr6DThVhChbaRD+VjRIvhw=
X-Google-Smtp-Source: ABdhPJymWfSXIeWfz+CWDiD7bCUjr1MtFq/iIkJQozPvtMxjsFxsqq8eL3N+IA3XrxQj+hveuAMUxdPA8CQC6J1gHTk=
X-Received: by 2002:a05:6e02:20e8:: with SMTP id
q8mr23139801ilv.90.1620683498170;
Mon, 10 May 2021 14:51:38 -0700 (PDT)
MIME-Version: 1.0
References: <6do5xN2g5LPnFeM55iJ-4C4MyXOu_KeXxy68Xt4dJQMhi3LJ8ZrLICmEUlh8JGfDmsDG12m1JDAh0e0huwK_MlyKpdfn22ru3zsm7lYLfBo=@protonmail.com>
<CAJowKg+QM94g+JcC-E-NGD4J9-nXHWt5kBw14bXTAWaqZz=bYw@mail.gmail.com>
<CALeFGL02d9NVp+yobrtc2g6k2nBjBj0Qb==3Ukkbi8C_zb5qMg@mail.gmail.com>
In-Reply-To: <CALeFGL02d9NVp+yobrtc2g6k2nBjBj0Qb==3Ukkbi8C_zb5qMg@mail.gmail.com>
From: Jeremy <jlrubin@mit.edu>
Date: Mon, 10 May 2021 14:51:26 -0700
X-Gmail-Original-Message-ID: <CAD5xwhi1G3Jj3FAAWQP3BXTK34ugDQY32hq-cQnt8Ny8JP4eGQ@mail.gmail.com>
Message-ID: <CAD5xwhi1G3Jj3FAAWQP3BXTK34ugDQY32hq-cQnt8Ny8JP4eGQ@mail.gmail.com>
To: Keagan McClelland <keagan.mcclelland@gmail.com>,
Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary="00000000000033ae4305c200c828"
Cc: SatoshiSingh <SatoshiSingh@protonmail.com>
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: Mon, 10 May 2021 21:51:41 -0000
--00000000000033ae4305c200c828
Content-Type: text/plain; charset="UTF-8"
re: 2, there's been some promising developments with Verifiable Delay
Functions that make me think that the block regulation problems are
solvable without requiring brute-force search proof of work. Are those
inapplicable for some reason?
--00000000000033ae4305c200c828
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div style=3D"font-family:arial,helvetica,sans-serif;font-=
size:small;color:rgb(0,0,0)" class=3D"gmail_default">re: 2, there's bee=
n some promising developments with Verifiable Delay Functions that make me =
think that the block regulation problems are solvable without requiring bru=
te-force search proof of work. Are those inapplicable for some reason?<br><=
/div><div><div style=3D"font-family:arial,helvetica,sans-serif;font-size:sm=
all;color:rgb(0,0,0)" class=3D"gmail_default"></div><br></div></div>
--00000000000033ae4305c200c828--
|
