From: Christian Moss <chrismoss411@gmail•com>
To: Peter Todd <pete@petertodd•org>
Cc: "Bitcoin Protocol Discussion"
<bitcoin-dev@lists•linuxfoundation.org>,
"Héctor José Cárdenas Pacheco" <hcarpach@gmail•com>,
lightning-dev <lightning-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] [Lightning-dev] Sending OP_RETURN via Bitcoin Lightning
Date: Thu, 9 Dec 2021 09:49:11 +0000 [thread overview]
Message-ID: <CANQKmg+D22GrLFDBAawop1uha3GG5F4TmixMajcTPQUdTF4-PQ@mail.gmail.com> (raw)
In-Reply-To: <YbHImwix1z8BgAc2@petertodd.org>
[-- Attachment #1: Type: text/plain, Size: 887 bytes --]
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
>
[-- Attachment #2: Type: text/html, Size: 1504 bytes --]
next prev parent reply other threads:[~2021-12-09 9:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-06 9:54 [bitcoin-dev] " Héctor José Cárdenas Pacheco
2021-12-06 10:20 ` Karl
2021-12-06 11:31 ` [bitcoin-dev] [Lightning-dev] " Martin Habovštiak
2021-12-06 16:35 ` Christian Moss
2021-12-09 9:12 ` Peter Todd
2021-12-09 9:49 ` Christian Moss [this message]
2021-12-09 10:07 ` Peter Todd
2021-12-09 12:12 ` Alex Schoof
2021-12-09 12:56 ` Peter Todd
2021-12-06 12:38 ` [bitcoin-dev] " Christian Moss
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CANQKmg+D22GrLFDBAawop1uha3GG5F4TmixMajcTPQUdTF4-PQ@mail.gmail.com \
--to=chrismoss411@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=hcarpach@gmail$(echo .)com \
--cc=lightning-dev@lists$(echo .)linuxfoundation.org \
--cc=pete@petertodd$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox