From: Karl <gmkarl@gmail•com>
To: "Héctor José Cárdenas Pacheco" <hcarpach@gmail•com>,
"Bitcoin Protocol Discussion"
<bitcoin-dev@lists•linuxfoundation.org>
Cc: lightning-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] Sending OP_RETURN via Bitcoin Lightning
Date: Mon, 6 Dec 2021 05:20:55 -0500 [thread overview]
Message-ID: <CALL-=e5mF9TqbbD=Cf-bawbw4dq2PGjC9W_nqAQeHsB829ZpNg@mail.gmail.com> (raw)
In-Reply-To: <DD7D5A8B-F61F-4302-ACF4-CE731843D97D@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1948 bytes --]
Hi,
I'm not a bitcoin developer.
On Mon, Dec 6, 2021, 5:05 AM Héctor José Cárdenas Pacheco via bitcoin-dev <
bitcoin-dev@lists•linuxfoundation.org> wrote:
> Hello all,
>
> I’ve been thinking about how OP_RETURN is being used to create and trade
> NFTs on Bitcoin (think RarePepes, SoG and other new ones) and was wondering
> if it’s possible to
>
Do you have a link to any of these protocols?
make transactions with this opcode via Lightning.
>
> More specific questions could be:
>
> 1. Can opcodes like OP_RETURN be inside a channel’s opening or closing
> transaction?
> 2. If so, could that OP_RETURN change hands within that channel or
> network of channels?
>
> OP_RETURNs do not have ownership according to the bitcoin network. It is
not hard to define a protocol that associates an OP_RETURN with ownership,
and ownership could then be transferred via lightning by sending associated
currency via lightning. Robustness improvements seem possible.
> 1. If possible, could the OP_RETURN be divisible? Could one person
> send a piece of a OP_RETURN just like one can do right now on the primary
> ledger or would it need to maintain the OP_RETURN code intact?
>
> OP_RETURNs themselves do not have ownership, but you can define a protocol
that gives them divisible ownership, including via lightning.
I’m assuming that, if possible, this would need a protocol layer parallel
> to Bitcoin/Lightning that stores and reads all Bitcoin transactions and the
> ones which involve the node's channels as well as the ones with the
> OP_RETURN, just like CounterParty does right now with the primary ledger.
>
> Thank in advance.
> ——
>
> *Héctor Cárdenas*@hcarpach
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists•linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
[-- Attachment #2: Type: text/html, Size: 4496 bytes --]
next prev parent reply other threads:[~2021-12-06 10:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-06 9:54 Héctor José Cárdenas Pacheco
2021-12-06 10:20 ` Karl [this message]
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
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='CALL-=e5mF9TqbbD=Cf-bawbw4dq2PGjC9W_nqAQeHsB829ZpNg@mail.gmail.com' \
--to=gmkarl@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=hcarpach@gmail$(echo .)com \
--cc=lightning-dev@lists$(echo .)linuxfoundation.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