đź“… Original date posted:2021-12-06
đź“ť Original message:I recommend you researching RGB: https://rgb-org.github.io/
On Mon, Dec 6, 2021, 11:21 Karl <gmkarl at gmail.com> wrote:
> 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 at 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 at lists.linuxfoundation.org
>> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>>
> _______________________________________________
> Lightning-dev mailing list
> Lightning-dev at lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/lightning-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20211206/d86e56cb/attachment.html>;
Martin Habovštiak [ARCHIVE] /
npub186…y2s83
2023-06-07 23:00:51
in reply to nevent1q…3ncw
Author Public Key
npub186h7xm74e8dqvz64kzhx8aq3j47lwf3emlxl7w8j0d0thrth65vs9y2s83Published at
2023-06-07 23:00:51Event JSON
{
"id": "bad5d6e44d6478e8f70c4f600c14c4ba3cb8d59e1b3b99eb44f2f3e8e88aee28",
"pubkey": "3eafe36fd5c9da060b55b0ae63f411957df72639dfcdff38f27b5ebb8d77d519",
"created_at": 1686178851,
"kind": 1,
"tags": [
[
"e",
"97b5e00e1be3178d6cf7aa01780cf6ce95fda0db98cd98076f9fdb70146b4136",
"",
"reply"
],
[
"p",
"a23dbf6c6cc83e14cc3df4e56cc71845f611908084cfe620e83e40c06ccdd3d0"
]
],
"content": "📅 Original date posted:2021-12-06\n📝 Original message:I recommend you researching RGB: https://rgb-org.github.io/\n\nOn Mon, Dec 6, 2021, 11:21 Karl \u003cgmkarl at gmail.com\u003e wrote:\n\n\u003e Hi,\n\u003e\n\u003e I'm not a bitcoin developer.\n\u003e\n\u003e On Mon, Dec 6, 2021, 5:05 AM Héctor José Cárdenas Pacheco via bitcoin-dev \u003c\n\u003e bitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\u003e\n\u003e\u003e Hello all,\n\u003e\u003e\n\u003e\u003e I’ve been thinking about how OP_RETURN is being used to create and trade\n\u003e\u003e NFTs on Bitcoin (think RarePepes, SoG and other new ones) and was wondering\n\u003e\u003e if it’s possible to\n\u003e\u003e\n\u003e\n\u003e Do you have a link to any of these protocols?\n\u003e\n\u003e make transactions with this opcode via Lightning.\n\u003e\u003e\n\u003e\u003e More specific questions could be:\n\u003e\u003e\n\u003e\u003e 1. Can opcodes like OP_RETURN be inside a channel’s opening or\n\u003e\u003e closing transaction?\n\u003e\u003e 2. If so, could that OP_RETURN change hands within that channel or\n\u003e\u003e network of channels?\n\u003e\u003e\n\u003e\u003e OP_RETURNs do not have ownership according to the bitcoin network. It is\n\u003e not hard to define a protocol that associates an OP_RETURN with ownership,\n\u003e and ownership could then be transferred via lightning by sending associated\n\u003e currency via lightning. Robustness improvements seem possible.\n\u003e\n\u003e\n\u003e\u003e 1. If possible, could the OP_RETURN be divisible? Could one person\n\u003e\u003e send a piece of a OP_RETURN just like one can do right now on the primary\n\u003e\u003e ledger or would it need to maintain the OP_RETURN code intact?\n\u003e\u003e\n\u003e\u003e OP_RETURNs themselves do not have ownership, but you can define a\n\u003e protocol that gives them divisible ownership, including via lightning.\n\u003e\n\u003e I’m assuming that, if possible, this would need a protocol layer parallel\n\u003e\u003e to Bitcoin/Lightning that stores and reads all Bitcoin transactions and the\n\u003e\u003e ones which involve the node's channels as well as the ones with the\n\u003e\u003e OP_RETURN, just like CounterParty does right now with the primary ledger.\n\u003e\u003e\n\u003e\u003e Thank in advance.\n\u003e\u003e ——\n\u003e\u003e\n\u003e\u003e *Héctor Cárdenas*@hcarpach\n\u003e\u003e\n\u003e\u003e _______________________________________________\n\u003e\u003e bitcoin-dev mailing list\n\u003e\u003e bitcoin-dev at lists.linuxfoundation.org\n\u003e\u003e https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev\n\u003e\u003e\n\u003e _______________________________________________\n\u003e Lightning-dev mailing list\n\u003e Lightning-dev at lists.linuxfoundation.org\n\u003e https://lists.linuxfoundation.org/mailman/listinfo/lightning-dev\n\u003e\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20211206/d86e56cb/attachment.html\u003e",
"sig": "dd2dd3ca1cc402a70e1264cc364e2ef94d7e44f726175cf7c6fbc40972a1f96c12ae0a07887aa594cb4a4d59ae9bdae51f66e4257697701f444b7ca0cb7e36db"
}