MIME-Version: 1.0
References: <DD7D5A8B-F61F-4302-ACF4-CE731843D97D@gmail.com>
 <CALL-=e5mF9TqbbD=Cf-bawbw4dq2PGjC9W_nqAQeHsB829ZpNg@mail.gmail.com>
 <CALkkCJas_pf7Un45CJyFg8j9cBk8PtKN4iYAL81TtLSRNnKqeg@mail.gmail.com>
 <CANQKmgLyaYAjL_=LziTCFT=Ahc2SXjJrWc+RO59pxd3mnJApfQ@mail.gmail.com>
 <YbHImwix1z8BgAc2@petertodd.org>
In-Reply-To: <YbHImwix1z8BgAc2@petertodd.org>
From: Christian Moss <chrismoss411@gmail.com>
Date: Thu, 9 Dec 2021 09:49:11 +0000
Message-ID: <CANQKmg+D22GrLFDBAawop1uha3GG5F4TmixMajcTPQUdTF4-PQ@mail.gmail.com>
To: Peter Todd <pete@petertodd.org>
Content-Type: multipart/alternative; boundary="00000000000064cb5705d2b3853b"
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>,
 =?UTF-8?Q?H=C3=A9ctor_Jos=C3=A9_C=C3=A1rdenas_Pacheco?=
 <hcarpach@gmail.com>, lightning-dev <lightning-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] [Lightning-dev] Sending OP_RETURN via Bitcoin
	Lightning
Precedence: list

--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 <pete@petertodd.org> 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

<div dir=3D"ltr"><a href=3D"mailto:pete@petertodd.org">pete@petertodd.org</=
a>, 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 int=
o the single tx going into the ledger?</div><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">On Thu, Dec 9, 2021 at 9:13 AM Peter =
Todd &lt;<a href=3D"mailto:pete@petertodd.org">pete@petertodd.org</a>&gt; w=
rote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0p=
x 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Mon, De=
c 06, 2021 at 04:35:19PM +0000, Christian Moss via bitcoin-dev wrote:<br>
&gt; As far as I understand it, RGB doesn&#39;t scale NFTs as each<br>
&gt; transaction to transfer ownership of an NFT would require an onchain<b=
r>
&gt; transaction<br>
<br>
RGB intends to scale NFTs and similar things in the future via scalable<br>
single-use-seals: <a href=3D"https://petertodd.org/2017/scalable-single-use=
-seal-asset-transfer" rel=3D"noreferrer" target=3D"_blank">https://petertod=
d.org/2017/scalable-single-use-seal-asset-transfer</a><br>
<br>
-- <br>
<a href=3D"https://petertodd.org" rel=3D"noreferrer" target=3D"_blank">http=
s://petertodd.org</a> &#39;peter&#39;[:-1]@<a href=3D"http://petertodd.org"=
 rel=3D"noreferrer" target=3D"_blank">petertodd.org</a><br>
</blockquote></div>

--00000000000064cb5705d2b3853b--