public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Peter Todd <pete@petertodd.org>
To: Christian Moss <chrismoss411@gmail.com>,
	Bitcoin Protocol Discussion
	<bitcoin-dev@lists.linuxfoundation.org>
Cc: lightning-dev <lightning-dev@lists.linuxfoundation.org>,
	"Héctor José Cárdenas Pacheco" <hcarpach@gmail.com>
Subject: Re: [bitcoin-dev] [Lightning-dev] Sending OP_RETURN via Bitcoin Lightning
Date: Thu, 9 Dec 2021 04:12:59 -0500	[thread overview]
Message-ID: <YbHImwix1z8BgAc2@petertodd.org> (raw)
In-Reply-To: <CANQKmgLyaYAjL_=LziTCFT=Ahc2SXjJrWc+RO59pxd3mnJApfQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 447 bytes --]

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: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2021-12-09  9:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-06  9:54 [bitcoin-dev] Sending OP_RETURN via Bitcoin Lightning 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 [this message]
2021-12-09  9:49         ` Christian Moss
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=YbHImwix1z8BgAc2@petertodd.org \
    --to=pete@petertodd.org \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=chrismoss411@gmail.com \
    --cc=hcarpach@gmail.com \
    --cc=lightning-dev@lists.linuxfoundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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