Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id F2BFBC2C for ; Sat, 29 Jun 2019 18:22:32 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from newmail.dtrt.org (li1228-87.members.linode.com [45.79.129.87]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 8D6D782F for ; Sat, 29 Jun 2019 18:22:32 +0000 (UTC) Received: from harding by newmail.dtrt.org with local (Exim 4.89) (envelope-from ) id 1hhHzb-0002Mb-F7; Sat, 29 Jun 2019 14:22:31 -0400 Date: Sat, 29 Jun 2019 14:21:03 -0400 From: "David A. Harding" To: Tamas Blummer , Bitcoin Protocol Discussion Message-ID: <20190629182103.sbbm4z54svxircbl@ganymede> References: <0DBC0DEA-C999-4AEE-B2E1-D5337ECD9405@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <0DBC0DEA-C999-4AEE-B2E1-D5337ECD9405@gmail.com> User-Agent: NeoMutt/20170113 (1.7.2) X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org X-Mailman-Approved-At: Sat, 29 Jun 2019 21:07:15 +0000 Subject: Re: [bitcoin-dev] Generalized covenants with taproot enable riskless or risky lending, prevent credit inflation through fractional reserve X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Bitcoin Protocol Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Jun 2019 18:22:33 -0000 On Fri, Jun 28, 2019 at 10:27:16AM +0200, Tamas Blummer via bitcoin-dev wrote: > The value of these outputs to Charlie is the proof that he has > exclusive control of the coins until maturity. > > Alice can not issue promissory notes in excess of own capital or > capital that she was able to borrow. No coin inflation or fractional > reserve here, which also reduces the credit risk Charlie takes. I believe these goals are obtainable today without any consensus changes. Bob can provably timelock bitcoins using CLTV or CSV in a script that commits to the outpoint (txid, vout) of an output that will be used as a colored coin to track the debt instrument. The colored coin, which has no appreciable onchain value itself, can then be trustlessly traded, e.g. from Alice to Charlie to Dan as you describe. Anyone with a copy of the script Bob paid, the confirmed transaction he included it in, and the confirmed transaction history of the colored coin can trustlessly verify the ownership record---including that no inflation or fractional reserve occurred. I believe the RGB working group has set for itself the goal[1] of making trustless colored coin protocols more efficient when performed on top of Bitcoin. I'd also suggest reading about Peter Todd's concept of single-use seals[2]. You may want to investigate these ideas and see whether they can be integrated with your own. [1] https://github.com/rgb-org/spec/blob/master/00-introduction.md [2] https://petertodd.org/2016/commitments-and-single-use-seals#bitcoin-transaction-outputs-as-single-use-seals -Dave