Return-Path: Received: from smtp1.osuosl.org (smtp1.osuosl.org [IPv6:2605:bc80:3010::138]) by lists.linuxfoundation.org (Postfix) with ESMTP id DC32DC0012; Thu, 9 Dec 2021 10:23:04 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp1.osuosl.org (Postfix) with ESMTP id BB22882C3B; Thu, 9 Dec 2021 10:23:04 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org X-Spam-Flag: NO X-Spam-Score: -2.398 X-Spam-Level: X-Spam-Status: No, score=-2.398 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: smtp1.osuosl.org (amavisd-new); dkim=fail (2048-bit key) reason="fail (message has been altered)" header.d=petertodd.org 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 NiMVK7pARYqI; Thu, 9 Dec 2021 10:23:03 +0000 (UTC) X-Greylist: delayed 00:15:15 by SQLgrey-1.8.0 X-Greylist: from auto-whitelisted by SQLgrey-1.8.0 Received: from outmail148102.authsmtp.net (outmail148102.authsmtp.net [62.13.148.102]) by smtp1.osuosl.org (Postfix) with ESMTPS id 2094A82AEF; Thu, 9 Dec 2021 10:23:02 +0000 (UTC) Received: from mail-c237.authsmtp.com (mail-c237.authsmtp.com [62.13.128.237]) by punt17.authsmtp.com. (8.15.2/8.15.2) with ESMTP id 1B9A7jqQ077285; Thu, 9 Dec 2021 10:07:45 GMT (envelope-from user@petertodd.org) Received: from petertodd.org (76-10-157-59.dsl.teksavvy.com [76.10.157.59]) (authenticated bits=0) by mail.authsmtp.com (8.15.2/8.15.2) with ESMTPSA id 1B9A7hoR024327 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 9 Dec 2021 10:07:44 GMT (envelope-from user@petertodd.org) Received: by petertodd.org (Postfix) with ESMTPSA id E008F9E4EE; Thu, 9 Dec 2021 05:07:41 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=petertodd.org; s=mail; t=1639044462; bh=u0bRM8IjH0r0NDbRISdDDKgkJxhEOfkAOqW/7MJe4TM=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=ig//lvRO4Ly9Z9btipUOdLYJ9YD62XJ8kslmRlyN9GDQtHTBv24dhqr4k/vPjLpbn tRmHHY1RMEkIKW1i10IArm3kkN0TrM21muW8Mr3NkEJUo7K1v9wHAaF0v3TSSUTAbU 587qsm07D+uykRshz1eZh0Jj374e5UNOpdc3orAOcRoLf4vDz8rTYi6lprL4t18yhj +Jw3Pw++YoT6977n8HjIr5FiGR/HcmJkpQU9ovpASsG/3Gekrh32UUwWzKfUdleBW0 9d9F4UX5AA96EPG75v+7T2WlFrVIP+YDkdmT8SOpMkBWN647Wm22fO8Z8ouCA9+cnn ZvEbyDWRaCzAw== Received: by localhost (Postfix, from userid 1000) id F3DC55FB4A; Thu, 9 Dec 2021 05:07:37 -0500 (EST) Date: Thu, 9 Dec 2021 05:07:37 -0500 From: Peter Todd To: Christian Moss Message-ID: References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="GdjUhLDGsLfybwJA" Content-Disposition: inline In-Reply-To: X-Server-Quench: da6ffe79-58d7-11ec-ba2e-8434971169dc X-AuthReport-Spam: If SPAM / abuse - report it at: http://www.authsmtp.com/abuse X-AuthRoute: OCd2Yg0TA1ZIVwkA IjsJECJaVQIpKltL GxAVKBZePFsRUQkR bwdMdgsUHFAXAgsB AWcbWlReUFp7XWc7 bAxPbAVDY09JQQBj T0pMXVMcFXdhcBtZ WXweUB1xdQIIeXZ1 YEMsCiFdChIvck9g R0YAEnAHZDIzdTJO UhVFfwdXdApNfx5D YwQsGhFYa3VsNCMk FAgyOXU9MCtqYBdx Qw4NMVQTR0lOEjMi clg5EDMjHEsKDwIL GCYLFmMmOg4PM0x6 G1o9UlUZNX1aLgxR H11LASlWTwAI X-Authentic-SMTP: 61633532353630.1024:7600 X-AuthFastPath: 0 (Was 255) X-AuthSMTP-Origin: 76.10.157.59/25 X-AuthVirus-Status: No virus detected - but ensure you scan with your own anti-virus system. Cc: Bitcoin Protocol Discussion , =?iso-8859-1?Q?H=E9ctor_Jos=E9_C=E1rdenas?= Pacheco , lightning-dev Subject: Re: [bitcoin-dev] [Lightning-dev] Sending OP_RETURN via Bitcoin Lightning 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: Thu, 09 Dec 2021 10:23:05 -0000 --GdjUhLDGsLfybwJA Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Dec 09, 2021 at 09:49:11AM +0000, Christian Moss wrote: > pete@petertodd.org, so single use seals require an onchain transaction to > post the proof of publication to the ledger (assuming bitcoin is used as > the ledger) when an asset is transferred, but it can scale because you can > batch many proofs (transfer of ownerships) into a merkle tree and just add > the merkle root into the single tx going into the ledger? Exactly. And since the aggregation is trustless with respect to validity, u= sers can choose what kind of censorship risk they're willing to take (as well as mitigate it with "multisig" schemes that use multiple aggregators in parall= el). --=20 https://petertodd.org 'peter'[:-1]@petertodd.org --GdjUhLDGsLfybwJA Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEE0RcYcKRzsEwFZ3N5Lly11TVRLzcFAmGx1WoACgkQLly11TVR Lzc7VRAAwIUvA1B2T3C4Oayka5GLtJt5CBP8W3pKmpFgZfjSHD1Ktq1U/iHXiV4D EA1Fd0VZbIPUXj2oR797f7AjoNagNJ5sVuqMvDNIGWpeqIhlXE0zXssSvHqL60Yv cOm2UVm/b+d1ASbb1YONNPOOB1QNuGGqjtzqsXwx8+TNbcdaELD77o9y9jn2Wa82 asXeZeOqsqjbuIm4ugRV1oMLZaER6tNf6WhAv2LzEOSLKsK/ZSaydmNHRKzinIef +o1YXW7PjjyoAOsvhiNAdePichtkJW3Hq5aE9wa2HRj4uVOE6cKLG55EhmgT5nXn Ayb4t6MvkIn5vtqbb5ow96oxtP/qXz2x40vNCofNsOl8Q4VpguiqctDCSVP/x6pQ /q2k661JtkStdHUiCF3QWZnuMTkVFz1COHQXEdo69an9qxNDyfaLHTN/cjPjsZUS fa5o1l/yAEGRy9MOfeQxlrmahEB9p+upqY+U4YAl2VcEmBdQtEuOCRWsMmNmCrik pPREcAT+uB+1WXUdt49CpBbMqZVh/wKyCg0Du+9WhOJqwMT3uSjXDB80P6luyrW3 8JmGJTXJD5Dxtyf84BOWW7o4Uko64dS9XyQGXsoz5a8F70yFRAYQO5jPkkVWKhyC dlRq2HPqIa3nBmVJWsP6fNOhRCyT1BaL1fyxU+YQ0PQ4idE3AQY= =KoPi -----END PGP SIGNATURE----- --GdjUhLDGsLfybwJA--