From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp2.osuosl.org (smtp2.osuosl.org [140.211.166.133]) by lists.linuxfoundation.org (Postfix) with ESMTP id 04397C0012; Thu, 9 Dec 2021 09:49:26 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp2.osuosl.org (Postfix) with ESMTP id E272940146; Thu, 9 Dec 2021 09:49:25 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org X-Spam-Flag: NO X-Spam-Score: -1.848 X-Spam-Level: X-Spam-Status: No, score=-1.848 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_ENVFROM_END_DIGIT=0.25, 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 p80kYGUg43VR; Thu, 9 Dec 2021 09:49:23 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.8.0 X-Greylist: whitelisted by SQLgrey-1.8.0 Received: from mail-ua1-x934.google.com (mail-ua1-x934.google.com [IPv6:2607:f8b0:4864:20::934]) by smtp2.osuosl.org (Postfix) with ESMTPS id AE8FA40125; Thu, 9 Dec 2021 09:49:23 +0000 (UTC) Received: by mail-ua1-x934.google.com with SMTP id y5so9643008ual.7; Thu, 09 Dec 2021 01:49:23 -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=SzXngsdcFTIakgnZoZif5cvpCui+HhBfz+vKm/WT5eo=; b=DWgJq9DjcYUGgMV7qzNCmTO0RUqBnWHWLAS5KonEtN5lFQNXg7aCoLMkMwnXVBKyje ATKn92IGKKN8SH27vWWFBV+DCRMCzmO6NTJmwaRqc8NI/koWvQokW3Qlw4isP2Q5Guob LaEuYXnzG8tdvE2XkgMrbhknmbP3NeG/biUgSVK3vqdZkLk5A2rVSmxgyS/EQiYHbYzV jX6x6WxY4itFmCzO26rMWfaYHp8wAhRTykrGnijw973wfLot8B8nT5BJXtcMkBeUyioF 4b5sUqirc4Yo2hYrddwwE/VG1bKq56X/N74JlMAvk4dOo/ZWJaIYaqi34umQ/tta9K63 PiZw== 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=SzXngsdcFTIakgnZoZif5cvpCui+HhBfz+vKm/WT5eo=; b=hWTG0e+I/yqqZbNlCPPtZkWuGRoQEsuLRxreEQOfu5ikRxnKTQIJrxiW8OpUhPK1cr q6qn5uav2QMksbG+eJOwxiZdb+zYGXiW3Xe/X2x6SjCTDDFUEfCj/a5JZSazbG5y6AYv 9CBcst7VuOw6gG9m451GVaPylDkkYNbdkkBgWzNzZZA3HT8Rc6d1sC6+ZFh6h4HGbmwl Pje/E2q3Ufs861vkETpOoLWk18QrexGLuLXqgOyoJ5H9Cca6YDj0zbeJ8eOpg+SlyT9N S5Oavk8b5kaV4Yxqz1+uLuEqT3u+/YYUagcmS/Nrl1oqEgd5LdrSDrdYLTlkZL2ikOIg ZRGQ== X-Gm-Message-State: AOAM530ZLxYEpaK9RWdwojubduemTnQAxSJMNdxzqwT36KxlOveSyi7Q O+2ou3voaIbYgyzz3DpErbIJy6+GRxafmhM6zNw= X-Google-Smtp-Source: ABdhPJw8H7EVhC1HajAFw56XQm8zY+x09iFJEewxb44uWOLMs+i4rrreFBZZ/T6K2YrXfbFu7AhwIHI6Unp72jLXOig= X-Received: by 2002:a05:6102:3029:: with SMTP id v9mr6108334vsa.46.1639043362506; Thu, 09 Dec 2021 01:49:22 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Christian Moss Date: Thu, 9 Dec 2021 09:49:11 +0000 Message-ID: To: Peter Todd Content-Type: multipart/alternative; boundary="00000000000064cb5705d2b3853b" X-Mailman-Approved-At: Thu, 09 Dec 2021 09:56:14 +0000 Cc: Bitcoin Protocol Discussion , =?UTF-8?Q?H=C3=A9ctor_Jos=C3=A9_C=C3=A1rdenas_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 09:49:26 -0000 --00000000000064cb5705d2b3853b Content-Type: text/plain; charset="UTF-8" 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? On Thu, Dec 9, 2021 at 9:13 AM Peter Todd wrote: > On Mon, Dec 06, 2021 at 04:35:19PM +0000, Christian Moss via bitcoin-dev > wrote: > > As far as I understand it, RGB doesn't scale NFTs as each > > transaction to transfer ownership of an NFT would require an onchain > > transaction > > RGB intends to scale NFTs and similar things in the future via scalable > single-use-seals: > https://petertodd.org/2017/scalable-single-use-seal-asset-transfer > > -- > https://petertodd.org 'peter'[:-1]@petertodd.org > --00000000000064cb5705d2b3853b Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
=
On Mon, De= c 06, 2021 at 04:35:19PM +0000, Christian Moss via bitcoin-dev wrote:
> As far as I understand it, RGB doesn't scale NFTs as each
> transaction to transfer ownership of an NFT would require an onchain > transaction

RGB intends to scale NFTs and similar things in the future via scalable
single-use-seals: https://petertod= d.org/2017/scalable-single-use-seal-asset-transfer

--
http= s://petertodd.org 'peter'[:-1]@petertodd.org
--00000000000064cb5705d2b3853b--