Return-Path: Received: from smtp1.osuosl.org (smtp1.osuosl.org [140.211.166.138]) by lists.linuxfoundation.org (Postfix) with ESMTP id 2D80DC000B for ; Sat, 5 Mar 2022 22:57:53 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp1.osuosl.org (Postfix) with ESMTP id 16FD6819D2 for ; Sat, 5 Mar 2022 22:57:53 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org X-Spam-Flag: NO X-Spam-Score: -1.599 X-Spam-Level: X-Spam-Status: No, score=-1.599 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, FROM_LOCAL_NOVOWEL=0.5, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: smtp1.osuosl.org (amavisd-new); dkim=pass (2048-bit key) header.d=protonmail.com Received: from smtp1.osuosl.org ([127.0.0.1]) by localhost (smtp1.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GO-5tghjvCI6 for ; Sat, 5 Mar 2022 22:57:51 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.8.0 Received: from mail-4319.protonmail.ch (mail-4319.protonmail.ch [185.70.43.19]) by smtp1.osuosl.org (Postfix) with ESMTPS id 0FF8D817AF for ; Sat, 5 Mar 2022 22:57:50 +0000 (UTC) Date: Sat, 05 Mar 2022 22:57:39 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail3; t=1646521068; bh=hDcZCk+3ZQgmICFSSyP+t8iYsHJ61cvYPJuffEVsGW0=; h=Date:To:From:Cc:Reply-To:Subject:Message-ID:In-Reply-To: References:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID; b=HG4oyWa49hY7oW12MWXttnYdRJfqh8u0eskexqSnYFAM05P7TV+Xx3mjZLJyRmHuC yjf/yfbdkjJ2PBl0G/0bMTxhMHsKo9pZ5dL7o1nMW6giZTP1+yure0gJ8i9Sgs8Sez sWBEsWRAw0xtXliyyBzK0Pyq8zfMzsElnydSGsiCBd+dWhTMrgfH8XfrkrSpsUn92h tHS63OBNh4IxDkR6r45ThgLm9vfmVNgU3FXA0DDFl4WUEX9OAYi4X8rtddQ3k7VPZy EYQCyWiOpve9lAlfzH/I2tQf4wXhiRUffq+AbPbDwtI/AsVpktUOnLBR6IjcRqxnqF m1ZvIIzc6c2sg== To: Chris Stewart From: ZmnSCPxj Reply-To: ZmnSCPxj Message-ID: <1ICs_kG6Eloiy6E4yLUkdFUI4EqKtaRPqcIY5kOM8Pq1xdWQHAMsMUxFsQ0xw2RcdMoMfxJSmlhb_ilXaw_nESliKxlE_Xp5tchQxXKD58E=@protonmail.com> In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: Bitcoin Protocol Discussion , "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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Mar 2022 22:57:53 -0000 Good morning Chris, > I think this proposal describes arbitrary lines of pre-approved credit fr= om a bitcoin wallet. The line can be drawn down with oracle attestations. Y= ou 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 s= pent 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 workperso= n 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 orac= le 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 c= an be spent, can also be implemented by a simple 2-of-3, and called an "esc= row". After all, the oracle attestation can be a partial signature as well, not j= ust 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