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