path: root/68/6d024d3090a894e5b2d2ad7dcae5cc09c84598

Return-Path: <jeremy.l.rubin@gmail.com>
Received: from smtp2.osuosl.org (smtp2.osuosl.org [IPv6:2605:bc80:3010::133])
 by lists.linuxfoundation.org (Postfix) with ESMTP id E5FA7C000B
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Sun,  6 Mar 2022 00:15:05 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by smtp2.osuosl.org (Postfix) with ESMTP id DA0E340198
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Sun,  6 Mar 2022 00:15:05 +0000 (UTC)
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 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, FREEMAIL_FROM=0.001,
 HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001,
 SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: smtp2.osuosl.org (amavisd-new);
 dkim=pass (2048-bit key) header.d=gmail.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 MbeoyQwxLqJ3
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Sun,  6 Mar 2022 00:15:04 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.8.0
Received: from mail-lj1-x22d.google.com (mail-lj1-x22d.google.com
 [IPv6:2a00:1450:4864:20::22d])
 by smtp2.osuosl.org (Postfix) with ESMTPS id 5E600400E4
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Sun,  6 Mar 2022 00:15:04 +0000 (UTC)
Received: by mail-lj1-x22d.google.com with SMTP id q5so990907ljb.11
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Sat, 05 Mar 2022 16:15:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112;
 h=mime-version:references:in-reply-to:from:date:message-id:subject:to
 :cc; bh=MugdlZIDByUAodgS04F6INnvzD1/vh+flMgYNgKQdrs=;
 b=GWeKGrlKpYyD2XUbDvw5QJf545TyWIGW/3OiMYwqU888KoFy/QPITqLNjMmoNVjwbK
 fhDG1B3e+ylQJKdM7NlTrcfhbuK1VjLBF6Dk8zTuXuh07WXjPZPa/CWywZT5QkZF0EVK
 2rGMXmYub+AMZ6PO5edno0vvN5sv3KFf+wrw9jsEMqQcChIjV4qVriTJuCHr7T1hwaen
 lVLMwb9R9is2iIg0OmdtJ2+pGSzDaSHfqODuEECayhIhyv4+Xnzrkr1QIA2xmvNmNkJa
 Ol+ivyk4EomNpjFVlYwvhmvToUTp8rtzrLsXJqkhiOaTZa/BHgmpAqksBdAEvG58m2QQ
 7ciA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20210112;
 h=x-gm-message-state:mime-version:references:in-reply-to:from:date
 :message-id:subject:to:cc;
 bh=MugdlZIDByUAodgS04F6INnvzD1/vh+flMgYNgKQdrs=;
 b=uNMbveJGXGiwRJsaBlCVwuFFxYPeA8QevTLrm6e5P+tIftACYWyNZ6Cec0M1N2aphY
 3H6YptBOm4iIbWtH8eU528PCwxrhFBMk1iIjdU59j79TMHuWSaaHM5gSKJgHX+QO+5Ji
 8SeqpQuhnT0C5s1sqgejbuE+6qA5ZiUgotfCWuhhOgYYRkVBGFO9HlAlK3Y7rIF1HZyy
 /u7c5pqaZ0YUkj+5W6pUE85QM5QrpJlHa9yJCLpEYwM3m1ZOvXiDgbsopF1OjVaGZjis
 CStnZlWQmmgegChDMIdCqLJfXnrqb8gmxtP9wVNmCsSdaKDcwySpSryVNpClSYOcmETm
 HKRw==
X-Gm-Message-State: AOAM5339DT58tk9uIHcUkvEgpdQB+xEogc6MT9NdltLsaQBa0cvMHeKe
 04x8w7XlhopQNhF5d9JafRqlYN2ZUDmhOCZljpo=
X-Google-Smtp-Source: ABdhPJxdBEILYctwbUitq/SpxjeG8YoVu9jpIzPqgf+sXBKbdbaALgY2Mtlb7x8/d3WAWvJR8h+XPX0dmdufpsxqDWs=
X-Received: by 2002:a2e:a37a:0:b0:22d:7f2b:23c with SMTP id
 i26-20020a2ea37a000000b0022d7f2b023cmr3344201ljn.81.1646525702170; Sat, 05
 Mar 2022 16:15:02 -0800 (PST)
MIME-Version: 1.0
References: <CAFQwNuyqJCRYpCEOUFOS54k-Eu5SrkjhcUzk8-4zYK0tYhvX=A@mail.gmail.com>
 <MhqXmoLUj9JwcnZOETQr9lMMsbR_o75DrOG-v1Fz6FN571n31EgGAJUaSGOvMCSmDBSaI4hjAqtl5mLAWTnOjbWHAaJPzrpl06vhmt5xXSI=@protonmail.com>
 <CAFQwNuxaphkKbVwFdmRRJ7DX2tqMpvfk=8syuBXTTqJ2qBW9rg@mail.gmail.com>
 <1ICs_kG6Eloiy6E4yLUkdFUI4EqKtaRPqcIY5kOM8Pq1xdWQHAMsMUxFsQ0xw2RcdMoMfxJSmlhb_ilXaw_nESliKxlE_Xp5tchQxXKD58E=@protonmail.com>
In-Reply-To: <1ICs_kG6Eloiy6E4yLUkdFUI4EqKtaRPqcIY5kOM8Pq1xdWQHAMsMUxFsQ0xw2RcdMoMfxJSmlhb_ilXaw_nESliKxlE_Xp5tchQxXKD58E=@protonmail.com>
From: Jeremy Rubin <jeremy.l.rubin@gmail.com>
Date: Sun, 6 Mar 2022 00:14:51 +0000
Message-ID: <CAD5xwhjgLG0sVS3Zy5=tJt8cdgj75L4Us1SDZDcw6ZO1Juc=NA@mail.gmail.com>
To: ZmnSCPxj <ZmnSCPxj@protonmail.com>, 
 Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary="000000000000976ad605d981a38d"
Cc: "dlc-dev@mailmanlists.org" <dlc-dev@mailmanlists.org>
Subject: Re: [bitcoin-dev] Recurring bitcoin/LN payments using DLCs
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: Sun, 06 Mar 2022 00:15:06 -0000

--000000000000976ad605d981a38d
Content-Type: text/plain; charset="UTF-8"

This may be of interest:

https://github.com/sapio-lang/sapio/blob/01830132bbbe39c3225e173e099f6e1a0611461c/sapio/examples/subscription.py

Basically, a (old, python) sapio contract whereby you can make cancellable
subscriptions that are essentially a time based autopay scheme whereby
cancellation gives time for the receiver to claim the correct amount of
money.

--
@JeremyRubin <https://twitter.com/JeremyRubin>

On Sat, Mar 5, 2022 at 10:58 PM ZmnSCPxj via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:

> Good morning Chris,
>
> > I think this proposal describes arbitrary lines of pre-approved credit
> from a bitcoin wallet. The line can be drawn down with oracle attestations.
> You can mix in locktimes on these pre-approved lines of credit if you would
> like to rate limit, or ignore rate limiting and allow the full utxo to be
> spent by the borrower. It really is contextual to the use case IMO.
>
> Ah, that seems more useful.
>
> Here is an example application that might benefit from this scheme:
>
> I am commissioning some work from some unbranded workperson.
> I do not know how long the work will take, and I do not trust the
> workperson to accurately tell me how complete the work is.
> However, both I and the workperson trust a branded third party (the
> oracle) who can judge the work for itself and determine if it is complete
> or not.
> So I create a transaction whose signature can be completed only if the
> oracle releases a proper scalar and hand it over to the workperson.
> Then the workperson performs the work, then asks the oracle to judge if
> the work has been completed, and if so, the work can be compensated.
>
> On the other hand, the above, where the oracle determines *when* the fund
> can be spent, can also be implemented by a simple 2-of-3, and called an
> "escrow".
> After all, the oracle attestation can be a partial signature as well, not
> just a scalar.
> Is there a better application for this scheme?
>
> I suppose if the oracle attestation is intended to be shared among
> multiple such transactions?
> There may be multiple PTLCs, that are triggered by a single oracle?
>
> Regards,
> ZmnSCPxj
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>

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

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:arial,he=
lvetica,sans-serif;font-size:small;color:#000000">This may be of interest:<=
/div><div class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans=
-serif;font-size:small;color:#000000"><br></div><div class=3D"gmail_default=
" style=3D"font-family:arial,helvetica,sans-serif;font-size:small;color:#00=
0000"><a href=3D"https://github.com/sapio-lang/sapio/blob/01830132bbbe39c32=
25e173e099f6e1a0611461c/sapio/examples/subscription.py">https://github.com/=
sapio-lang/sapio/blob/01830132bbbe39c3225e173e099f6e1a0611461c/sapio/exampl=
es/subscription.py</a><br></div><div class=3D"gmail_default" style=3D"font-=
family:arial,helvetica,sans-serif;font-size:small;color:#000000"><br></div>=
<div class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-seri=
f;font-size:small;color:#000000">Basically, a (old, python) sapio contract =
whereby you can make cancellable subscriptions that are essentially a time =
based autopay scheme whereby cancellation gives time for the receiver=C2=A0=
to claim the correct amount of money.</div><br clear=3D"all"><div><div dir=
=3D"ltr" class=3D"gmail_signature" data-smartmail=3D"gmail_signature"><div =
dir=3D"ltr">--<br><a href=3D"https://twitter.com/JeremyRubin" target=3D"_bl=
ank">@JeremyRubin</a><br></div></div></div></div><br><div class=3D"gmail_qu=
ote"><div dir=3D"ltr" class=3D"gmail_attr">On Sat, Mar 5, 2022 at 10:58 PM =
ZmnSCPxj via bitcoin-dev &lt;<a href=3D"mailto:bitcoin-dev@lists.linuxfound=
ation.org">bitcoin-dev@lists.linuxfoundation.org</a>&gt; wrote:<br></div><b=
lockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-le=
ft-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);pad=
ding-left:1ex">Good morning Chris,<br>
<br>
&gt; I think this proposal describes arbitrary lines of pre-approved credit=
 from a bitcoin wallet. The line can be drawn down with oracle attestations=
. You can mix in locktimes on these pre-approved lines of credit if you wou=
ld like to rate limit, or ignore rate limiting and allow the full utxo to b=
e spent by the borrower. It really is contextual to the use case IMO.<br>
<br>
Ah, that seems more useful.<br>
<br>
Here is an example application that might benefit from this scheme:<br>
<br>
I am commissioning some work from some unbranded workperson.<br>
I do not know how long the work will take, and I do not trust the workperso=
n to accurately tell me how complete the work is.<br>
However, both I and the workperson trust a branded third party (the oracle)=
 who can judge the work for itself and determine if it is complete or not.<=
br>
So I create a transaction whose signature can be completed only if the orac=
le releases a proper scalar and hand it over to the workperson.<br>
Then the workperson performs the work, then asks the oracle to judge if the=
 work has been completed, and if so, the work can be compensated.<br>
<br>
On the other hand, the above, where the oracle determines *when* the fund c=
an be spent, can also be implemented by a simple 2-of-3, and called an &quo=
t;escrow&quot;.<br>
After all, the oracle attestation can be a partial signature as well, not j=
ust a scalar.<br>
Is there a better application for this scheme?<br>
<br>
I suppose if the oracle attestation is intended to be shared among multiple=
 such transactions?<br>
There may be multiple PTLCs, that are triggered by a single oracle?<br>
<br>
Regards,<br>
ZmnSCPxj<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>

--000000000000976ad605d981a38d--