MIME-Version: 1.0
References: <CALZpt+FhpZETHP8UpDGgw-Wg=m4Hxm8y9XZ9kXYgmt90_6Zt6w@mail.gmail.com>
 <CAHUJnBDu+PNvER-FmpT8593vX-wAZ1oPWJjQaJ=d7Y4pso_Txw@mail.gmail.com>
In-Reply-To: <CAHUJnBDu+PNvER-FmpT8593vX-wAZ1oPWJjQaJ=d7Y4pso_Txw@mail.gmail.com>
From: Antoine Riard <antoine.riard@gmail.com>
Date: Mon, 25 Jul 2022 23:21:11 -0400
Message-ID: <CALZpt+E4Ej3KJ4WqkUDTF3DRhPTbUT5mw2c_eHLuxH7w1BbWGg@mail.gmail.com>
To: Bram Cohen <bram@chia.net>
Content-Type: multipart/alternative; boundary="00000000000077bb4305e4accbba"
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] On a new community process to specify covenants
Precedence: list

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

What would be the canonical definition and examples of capabilities in the
Bitcoin context ?

In anycase, I believe it would be better to start a covenant process from
the use-cases in themselves, and analyse the trade-offs of any set of
contracting primitives, or even new Bitcoin fields if they're required
building blocks of the use-cases.

Le dim. 24 juil. 2022 =C3=A0 14:23, Bram Cohen <bram@chia.net> a =C3=A9crit=
 :

> On Wed, Jul 20, 2022 at 2:46 PM Antoine Riard via bitcoin-dev <
> bitcoin-dev@lists.linuxfoundation.org> wrote:
>
>> Indeed this range has grown wild. Without aiming to be exhaustive (I'm
>> certainly missing some interesting proposals lost in the abyss of
>> bitcointalk.org), we can mention the following use-cases: multi-party
>> stateful contracts [11], congestion trees [12], payment pools [13], "elt=
oo"
>> layered commitments [14], programmable vaults [15], multi-events contrac=
ts
>> [16], blockchain-as-oracle bets [17], spacechains [18], trustless
>> collateral lending [19], ...
>>
>
> The big question you missed is whether capabilities are in scope for a
> covenants proposal. In particular, vaults work a lot better when payments
> to them are immediately locked up in the vault rather than it having to d=
o
> a step to accept them first.
>

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

<div dir=3D"ltr">What would be the canonical definition and examples of cap=
abilities in the Bitcoin context ?<br><br>In anycase, I believe it would be=
 better to start a covenant process from the use-cases in themselves, and a=
nalyse the trade-offs of any set of contracting primitives, or even new Bit=
coin fields if they&#39;re required building blocks of the use-cases.<br></=
div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">Le=
=C2=A0dim. 24 juil. 2022 =C3=A0=C2=A014:23, Bram Cohen &lt;<a href=3D"mailt=
o:bram@chia.net">bram@chia.net</a>&gt; a =C3=A9crit=C2=A0:<br></div><blockq=
uote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1p=
x solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div dir=3D"ltr=
">On Wed, Jul 20, 2022 at 2:46 PM Antoine Riard via bitcoin-dev &lt;<a href=
=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank">bitcoin=
-dev@lists.linuxfoundation.org</a>&gt; wrote:<br></div><div class=3D"gmail_=
quote"><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">I=
ndeed this range has grown wild. Without aiming to be exhaustive (I&#39;m c=
ertainly missing some interesting proposals lost in the abyss of <a href=3D=
"http://bitcointalk.org" target=3D"_blank">bitcointalk.org</a>), we can men=
tion the following use-cases: multi-party stateful contracts [11], congesti=
on trees [12], payment pools [13], &quot;eltoo&quot; layered commitments [1=
4], programmable vaults [15], multi-events contracts [16], blockchain-as-or=
acle bets [17], spacechains [18], trustless collateral lending [19], ...<br=
></div></blockquote><div><br></div><div>The big question you missed is whet=
her capabilities are in scope for a covenants proposal. In particular, vaul=
ts work a lot better when payments to them are immediately locked up in the=
 vault rather than it having to do a step to accept them first.</div></div>=
</div>
</blockquote></div>

--00000000000077bb4305e4accbba--