From: "Héctor José Cárdenas Pacheco" <hcarpach@gmail•com>
To: bitcoin-dev@lists•linuxfoundation.org
Cc: lightning-dev@lists•linuxfoundation.org
Subject: [bitcoin-dev] Sending OP_RETURN via Bitcoin Lightning
Date: Mon, 6 Dec 2021 06:54:30 -0300 [thread overview]
Message-ID: <DD7D5A8B-F61F-4302-ACF4-CE731843D97D@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1003 bytes --]
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 make transactions with this opcode via Lightning.
More specific questions could be:
Can opcodes like OP_RETURN be inside a channel’s opening or closing transaction?
If so, could that OP_RETURN change hands within that channel or network of channels?
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?
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
[-- Attachment #2: Type: text/html, Size: 1929 bytes --]
next reply other threads:[~2021-12-06 9:54 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 [this message]
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
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=DD7D5A8B-F61F-4302-ACF4-CE731843D97D@gmail.com \
--to=hcarpach@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--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