Return-Path: Received: from smtp2.osuosl.org (smtp2.osuosl.org [140.211.166.133]) by lists.linuxfoundation.org (Postfix) with ESMTP id 6458BC0001 for ; 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 ; 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 ; 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 ; 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 ; Mon, 10 May 2021 17:51:38 -0400 Received: by mail-il1-f176.google.com with SMTP id l19so15389563ilk.13 for ; 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> In-Reply-To: From: Jeremy Date: Mon, 10 May 2021 14:51:26 -0700 X-Gmail-Original-Message-ID: Message-ID: To: Keagan McClelland , Bitcoin Protocol Discussion Content-Type: multipart/alternative; boundary="00000000000033ae4305c200c828" Cc: SatoshiSingh 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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
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?
<= /div>

--00000000000033ae4305c200c828--