Return-Path: Received: from smtp2.osuosl.org (smtp2.osuosl.org [140.211.166.133]) by lists.linuxfoundation.org (Postfix) with ESMTP id 3C001C000E for ; Mon, 28 Jun 2021 17:38:12 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp2.osuosl.org (Postfix) with ESMTP id 1D8A14022B for ; Mon, 28 Jun 2021 17:38:12 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org X-Spam-Flag: NO X-Spam-Score: -2.8 X-Spam-Level: X-Spam-Status: No, score=-2.8 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, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: smtp2.osuosl.org (amavisd-new); dkim=pass (1024-bit key) header.d=riseup.net 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 LbbyCH8qv-ev for ; Mon, 28 Jun 2021 17:38:11 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.8.0 Received: from mx1.riseup.net (mx1.riseup.net [198.252.153.129]) by smtp2.osuosl.org (Postfix) with ESMTPS id 616E3400E5 for ; Mon, 28 Jun 2021 17:38:11 +0000 (UTC) Received: from fews2.riseup.net (fews2-pn.riseup.net [10.0.1.84]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.riseup.net", Issuer "Sectigo RSA Domain Validation Secure Server CA" (not verified)) by mx1.riseup.net (Postfix) with ESMTPS id 4GDFFG73tkzDq8G; Mon, 28 Jun 2021 10:38:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak; t=1624901891; bh=dNjUohCll2SvEZRo03FTXNmyVQgWR4Btl6TF/Kp6akM=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=BMq7/29+tOgmJrsOd57gkQVTsukUsfNEzjBBU4KgAAWv/e/iKP3aG39bM98ZstSwN vZR09uvzDGM1by1f2dwQpgGz8MEVfJsnHElIuLiRbVF+Hxc1hOebdL07B4CW6RiLqX Z+IfTot6JIk9g5k7QSib+LrfEbs1NEOR6m8pD9/I= X-Riseup-User-ID: F2F238111E38FADB468CA9EF3360E7DBD175C5D02CA41FF7974A47CA8BF3CB3C Received: from [127.0.0.1] (localhost [127.0.0.1]) by fews2.riseup.net (Postfix) with ESMTPSA id 4GDFFG5m3Wz20ZS; Mon, 28 Jun 2021 10:38:10 -0700 (PDT) MIME-Version: 1.0 Date: Mon, 28 Jun 2021 10:38:10 -0700 From: raymo@riseup.net To: Tao Effect In-Reply-To: <361A8332-2815-4840-ACE1-CB790C9816F5@taoeffect.com> References: <6leV9mViysrSOipJqrCM3wbqBOMO2gWI3BuEn0VKmaDf7GpawWyUIWLu-ddypMri7YeVmw94HNSaQYYp8fIkjZ0S3OtFTPQa6h9pkLprKDI=@protonmail.com> <9c2cec326adee1f4d4152e2195da0e7b@riseup.net> <361A8332-2815-4840-ACE1-CB790C9816F5@taoeffect.com> Message-ID: <24247e0d669750ed7d7754b4fc5491b4@riseup.net> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Mailman-Approved-At: Mon, 28 Jun 2021 17:44:48 +0000 Cc: Bitcoin Protocol Discussion Subject: Re: [bitcoin-dev] Boost Bitcoin circulation, Million Transactions Per Second with stronger privacy 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: Mon, 28 Jun 2021 17:38:12 -0000 Hi Greg, You are right, the whole scenario is: there is an issuer which own a UTXO issuers get fiat money or goods or services from creditor in exchange of a transaction. the transactions are intended to circulate in Sabu protocol instead of sending to Bitcoin network. creditor can not sign the transaction at all. instead he can ask issuer to change the balances (transaction outputs) and transfer some of his money to other creditor... here is complete paper to read it carefully: https://raymo-49157.medium.com/time-to-boost-bitcoin-circulation-million-transactions-per-second-and-privacy-1eef8568d180 Cheers Raymo On 2021-06-28 17:29, Tao Effect wrote: > Hi ZmnSCPxj & Raymo, > >> On Jun 28, 2021, at 8:28 AM, ZmnSCPxj via bitcoin-dev >> wrote: >> >> Good morning Raymo, >> >>> Hi ZmnSCPxj, >> >>> […] >> What prevents the creditor from signing a transaction that is >> neither a valid MT nor a GT? >> >> Nothing. > > How would the creditor create such a transaction? They need the > issuer’s private key, so they can’t create it? Am I > misunderstanding the scenario you’re describing? If so could you > give a more detailed description? > > Cheers, > Greg