diff options
author | Bram Cohen <bram@chia.net> | 2022-11-08 15:34:32 -0800 |
---|---|---|
committer | bitcoindev <bitcoindev@gnusha.org> | 2022-11-08 23:34:44 +0000 |
commit | fdf860cd6b33c129eb0f4f2409a6230da5816596 (patch) | |
tree | 178251e2f2660567e904c02a174a85b02007b4ce | |
parent | 88de7b8fe0ec1ccc608a5d4a9fc0bf9d8fac01b7 (diff) | |
download | pi-bitcoindev-fdf860cd6b33c129eb0f4f2409a6230da5816596.tar.gz pi-bitcoindev-fdf860cd6b33c129eb0f4f2409a6230da5816596.zip |
Re: [bitcoin-dev] Merkleize All The Things
-rw-r--r-- | 69/77bc4365b0e7b245a97a48b09b40eb0723e5c1 | 150 |
1 files changed, 150 insertions, 0 deletions
diff --git a/69/77bc4365b0e7b245a97a48b09b40eb0723e5c1 b/69/77bc4365b0e7b245a97a48b09b40eb0723e5c1 new file mode 100644 index 000000000..7625adeff --- /dev/null +++ b/69/77bc4365b0e7b245a97a48b09b40eb0723e5c1 @@ -0,0 +1,150 @@ +Return-Path: <bram@chia.net> +Received: from smtp3.osuosl.org (smtp3.osuosl.org [IPv6:2605:bc80:3010::136]) + by lists.linuxfoundation.org (Postfix) with ESMTP id ED252C002D + for <bitcoin-dev@lists.linuxfoundation.org>; + Tue, 8 Nov 2022 23:34:44 +0000 (UTC) +Received: from localhost (localhost [127.0.0.1]) + by smtp3.osuosl.org (Postfix) with ESMTP id BBB4860E0D + for <bitcoin-dev@lists.linuxfoundation.org>; + Tue, 8 Nov 2022 23:34:44 +0000 (UTC) +DKIM-Filter: OpenDKIM Filter v2.11.0 smtp3.osuosl.org BBB4860E0D +Authentication-Results: smtp3.osuosl.org; + dkim=pass (2048-bit key) header.d=chia.net header.i=@chia.net + header.a=rsa-sha256 header.s=google header.b=Tm0Lhsf8 +X-Virus-Scanned: amavisd-new at osuosl.org +X-Spam-Flag: NO +X-Spam-Score: -0.1 +X-Spam-Level: +X-Spam-Status: No, score=-0.1 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, HTML_MESSAGE=0.001, + PDS_OTHER_BAD_TLD=1.999, RCVD_IN_DNSWL_NONE=-0.0001, + SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no +Received: from smtp3.osuosl.org ([127.0.0.1]) + by localhost (smtp3.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) + with ESMTP id Q9KoEWmEG01D + for <bitcoin-dev@lists.linuxfoundation.org>; + Tue, 8 Nov 2022 23:34:43 +0000 (UTC) +X-Greylist: whitelisted by SQLgrey-1.8.0 +DKIM-Filter: OpenDKIM Filter v2.11.0 smtp3.osuosl.org CE6E8606C6 +Received: from mail-pg1-x52b.google.com (mail-pg1-x52b.google.com + [IPv6:2607:f8b0:4864:20::52b]) + by smtp3.osuosl.org (Postfix) with ESMTPS id CE6E8606C6 + for <bitcoin-dev@lists.linuxfoundation.org>; + Tue, 8 Nov 2022 23:34:43 +0000 (UTC) +Received: by mail-pg1-x52b.google.com with SMTP id q1so14698084pgl.11 + for <bitcoin-dev@lists.linuxfoundation.org>; + Tue, 08 Nov 2022 15:34:43 -0800 (PST) +DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chia.net; s=google; + h=to:subject:message-id:date:from:in-reply-to:references:mime-version + :from:to:cc:subject:date:message-id:reply-to; + bh=8y/0Q8oCYUiMWWf0SPKQddCLpPCvJmNbF2bwXP3cdQo=; + b=Tm0Lhsf84SaKBG0XXL6AbYXyisY9giteHftXSNOEGLQ3aWyO7QWUES/TBRzyTC0p10 + TLqNkI/HTSm4mRjp1frddPwi7MiOGZN0/xdbOB8XFKWSto3pdKlrZrbEmnJlezM7IqJr + TG+o7MmQxAuwmD5Vv34MDWzifHCW5yLxG2q2UYTLHSAuUFkqUagU1H/ntooGd7zR658k + JSakOQicuQYviJwZg1t26KErfaXO2svq7dFlCmq22BX6HPI3/ZEP55Hax330A38zJSM0 + Aab515UMO8LeHjomhy8dsFVnAc4T2NFt5CMN8PvGLHvs801xVVG4hozM4lMW9ppbYZ6F + ha2A== +X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; + d=1e100.net; s=20210112; + h=to:subject:message-id:date:from:in-reply-to:references:mime-version + :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; + bh=8y/0Q8oCYUiMWWf0SPKQddCLpPCvJmNbF2bwXP3cdQo=; + b=D3f4W11FUb6qD6AfCmB/dCzzmvPs01rx+9q2jfAWLzILJ2nNaJYw1mtl+DdG/uJrXR + F2m7gRmC3UaXj4bX39mqZjOPzReXU+ipUcAScwNyRPvr5Ml03iRni3K7I+BZOZ+vz+cJ + hjmHmMGfTQlVTSqK9DTf04ykMWjaHnZcMpoaF1fLHcUsKHgnjnvl+0jDxQeMzLHHqid+ + lLEo2L8bifhHtb1ebWGMjEKcYqqIvwX41rfGeugot5W9yjUjNzf6xi3akO/ep/MLy1m8 + fAp0fPL4x2/MF96pAJTluA6RTy0hhOCX9+rj56zrJ1Z3p75vuBvu9oePbxcPPIqVDE7e + M5vw== +X-Gm-Message-State: ACrzQf3NKzNJ8iHClSopeTWKgr68QhCGvLYCdvhnBU/2rCkXdNbbd/Lg + TuHpfmRgTPXZ2Jnls7ePoWV2izgyH/wYe3NGUIVSoQ== +X-Google-Smtp-Source: AMsMyM7OOpToGORRVO27PtWnTME3BcI+JPtLYB9JbI8JPWFZ096fikC8eTtYFfwAArHkhTdE+Ty0NRbIv5DHRxuBquk= +X-Received: by 2002:a05:6a00:3698:b0:56d:3180:e88f with SMTP id + dw24-20020a056a00369800b0056d3180e88fmr55528765pfb.66.1667950483127; Tue, 08 + Nov 2022 15:34:43 -0800 (PST) +MIME-Version: 1.0 +References: <CAMhCMoH9uZPeAE_2tWH6rf0RndqV+ypjbNzazpFwFnLUpPsZ7g@mail.gmail.com> +In-Reply-To: <CAMhCMoH9uZPeAE_2tWH6rf0RndqV+ypjbNzazpFwFnLUpPsZ7g@mail.gmail.com> +From: Bram Cohen <bram@chia.net> +Date: Tue, 8 Nov 2022 15:34:32 -0800 +Message-ID: <CAHUJnBA7PUy3ajygdvvBwg6EyhUXGA-KKL_bkXLKCRPS98kRqw@mail.gmail.com> +To: Salvatore Ingala <salvatore.ingala@gmail.com>, + Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org> +Content-Type: multipart/alternative; boundary="0000000000000cd12a05ecfdfcfb" +X-Mailman-Approved-At: Tue, 08 Nov 2022 23:52:07 +0000 +Subject: Re: [bitcoin-dev] Merkleize All The Things +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, 08 Nov 2022 23:34:45 -0000 + +--0000000000000cd12a05ecfdfcfb +Content-Type: text/plain; charset="UTF-8" + +On Tue, Nov 8, 2022 at 2:13 AM Salvatore Ingala via bitcoin-dev < +bitcoin-dev@lists.linuxfoundation.org> wrote: + +> +> I have been working on some notes to describe an approach that uses +> covenants in order to enable general smart contracts in bitcoin. You can +> find them here: +> +> https://merkle.fun/ +> <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev> +> + +Hash chained covenants in general all have about the same plateau of +functionality, which seems roughly reasonable to add to Bitcoin as it is +today but suffer from being limited and hence likely only a stepping stone +to greater functionality and unless whatever's put in now cleanly extends +to supporting more in the future it's likely to turn into a legacy +appendage which has to be supported. So my generic suggestion for this sort +of thing is that it should be proposed along with a plan for how it could +be extended to support full-blown covenants in the future. + +Another probably unhelpful bit of feedback I have is that Bitcoin should +probably be taking verkle trees seriously because those can have +substantially lower size/cost/weight than merkle trees. That doesn't just +apply to this proposal, but to Bitcoin in general, which doesn't seem to +have any serious verkle tree proposals to date. + +--0000000000000cd12a05ecfdfcfb +Content-Type: text/html; charset="UTF-8" +Content-Transfer-Encoding: quoted-printable + +<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">= +<div dir=3D"ltr" class=3D"gmail_attr">On Tue, Nov 8, 2022 at 2:13 AM Salvat= +ore Ingala via bitcoin-dev <<a href=3D"mailto:bitcoin-dev@lists.linuxfou= +ndation.org">bitcoin-dev@lists.linuxfoundation.org</a>> wrote:<br></div>= +<blockquote class=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"><br>I ha= +ve been working on some notes to describe an approach that uses covenants i= +n order to enable general smart contracts in bitcoin. You can find them her= +e:<div><br></div><div>=C2=A0 =C2=A0 <a href=3D"https://merkle.fun" target= +=3D"_blank">https://merkle.fun</a><a href=3D"https://lists.linuxfoundation.= +org/mailman/listinfo/bitcoin-dev" rel=3D"noreferrer" target=3D"_blank">/</a= +></div></div></blockquote><div><br></div><div>Hash chained covenants in gen= +eral all have about=C2=A0the same plateau of functionality, which seems rou= +ghly reasonable to add to Bitcoin as it is today but suffer from being limi= +ted and hence likely only a stepping stone to greater functionality and unl= +ess whatever's put in now cleanly extends to supporting more in the fut= +ure it's likely to turn into a legacy appendage which has to be support= +ed. So my generic suggestion for this sort of thing is that it should be pr= +oposed along with a plan for how it could be extended to support full-blown= + covenants in the future.</div><div><br></div><div>Another probably unhelpf= +ul bit of feedback I have is that Bitcoin should probably be taking verkle = +trees seriously because those can have substantially lower size/cost/weight= + than merkle trees. That doesn't just apply to this proposal, but to Bi= +tcoin in general, which doesn't seem to have any serious verkle tree pr= +oposals to date.</div></div></div> + +--0000000000000cd12a05ecfdfcfb-- + |