Bitcoin Error Log [ARCHIVE] on Nostr: š Original date posted:2021-12-06 š Original message: Omni Layer already does ...
š
Original date posted:2021-12-06
š Original message:
Omni Layer already does this, on Bitcoin, and recently added NFT support,
but I don't know much about that aspect.
OmniBOLT also exists as a LN layer for Omni assets. OB is being audited
right now.
Sending NFTs using Lightning is generally impractical, as it is a
liquidity-based routing network, thus requires a whole new network for each
new asset. But fungible assets should be doable by any popular token asset.
I don't think RGB is practically usable by anyone yet, and still needs
severe attention paid to auditing the design, if it is ever completed at
all...
On Mon, Dec 6, 2021 at 7:00 AM <
lightning-dev-request at lists.linuxfoundation.org> wrote:
> Send Lightning-dev mailing list submissions to
> lightning-dev at lists.linuxfoundation.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.linuxfoundation.org/mailman/listinfo/lightning-dev
> or, via email, send a message with subject or body 'help' to
> lightning-dev-request at lists.linuxfoundation.org
>
> You can reach the person managing the list at
> lightning-dev-owner at lists.linuxfoundation.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Lightning-dev digest..."
>
>
> Today's Topics:
>
> 1. Re: [bitcoin-dev] Sending OP_RETURN via Bitcoin Lightning (Karl)
> 2. Re: [bitcoin-dev] Sending OP_RETURN via Bitcoin Lightning
> (Martin Habov?tiak)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 6 Dec 2021 05:20:55 -0500
> From: Karl <gmkarl at gmail.com>
> To: H?ctor Jos? C?rdenas Pacheco <hcarpach at gmail.com>, Bitcoin
> Protocol Discussion <bitcoin-dev at lists.linuxfoundation.org>
> Cc: lightning-dev at lists.linuxfoundation.org
> Subject: Re: [Lightning-dev] [bitcoin-dev] Sending OP_RETURN via
> Bitcoin Lightning
> Message-ID:
> <CALL-=e5mF9TqbbD=
> Cf-bawbw4dq2PGjC9W_nqAQeHsB829ZpNg at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> 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
> >
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://lists.linuxfoundation.org/pipermail/lightning-dev/attachments/20211206/f3253ec4/attachment-0001.html
> >
>
> ------------------------------
>
> Message: 2
> Date: Mon, 6 Dec 2021 12:31:29 +0100
> From: Martin Habov?tiak <martin.habovstiak at gmail.com>
> To: Karl <gmkarl at gmail.com>
> Cc: Bitcoin Protocol Discussion
> <bitcoin-dev at lists.linuxfoundation.org>, lightning-dev
> <lightning-dev at lists.linuxfoundation.org>, H?ctor Jos? C?rdenas
> Pacheco <hcarpach at gmail.com>
> Subject: Re: [Lightning-dev] [bitcoin-dev] Sending OP_RETURN via
> Bitcoin Lightning
> Message-ID:
> <
> CALkkCJas_pf7Un45CJyFg8j9cBk8PtKN4iYAL81TtLSRNnKqeg at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> 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/lightning-dev/attachments/20211206/d86e56cb/attachment-0001.html
> >
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> Lightning-dev mailing list
> Lightning-dev at lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/lightning-dev
>
>
> ------------------------------
>
> End of Lightning-dev Digest, Vol 76, Issue 4
> ********************************************
>
--
~ John Carvalho
Schedule: https://calendly.com/bitcoinerrorlog
Chat: https://t.me/bitcoinerrorlog
Social: https://twitter.com/bitcoinerrorlog
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/lightning-dev/attachments/20211206/e4816d2d/attachment.html>;
š Original message:
Omni Layer already does this, on Bitcoin, and recently added NFT support,
but I don't know much about that aspect.
OmniBOLT also exists as a LN layer for Omni assets. OB is being audited
right now.
Sending NFTs using Lightning is generally impractical, as it is a
liquidity-based routing network, thus requires a whole new network for each
new asset. But fungible assets should be doable by any popular token asset.
I don't think RGB is practically usable by anyone yet, and still needs
severe attention paid to auditing the design, if it is ever completed at
all...
On Mon, Dec 6, 2021 at 7:00 AM <
lightning-dev-request at lists.linuxfoundation.org> wrote:
> Send Lightning-dev mailing list submissions to
> lightning-dev at lists.linuxfoundation.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.linuxfoundation.org/mailman/listinfo/lightning-dev
> or, via email, send a message with subject or body 'help' to
> lightning-dev-request at lists.linuxfoundation.org
>
> You can reach the person managing the list at
> lightning-dev-owner at lists.linuxfoundation.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Lightning-dev digest..."
>
>
> Today's Topics:
>
> 1. Re: [bitcoin-dev] Sending OP_RETURN via Bitcoin Lightning (Karl)
> 2. Re: [bitcoin-dev] Sending OP_RETURN via Bitcoin Lightning
> (Martin Habov?tiak)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 6 Dec 2021 05:20:55 -0500
> From: Karl <gmkarl at gmail.com>
> To: H?ctor Jos? C?rdenas Pacheco <hcarpach at gmail.com>, Bitcoin
> Protocol Discussion <bitcoin-dev at lists.linuxfoundation.org>
> Cc: lightning-dev at lists.linuxfoundation.org
> Subject: Re: [Lightning-dev] [bitcoin-dev] Sending OP_RETURN via
> Bitcoin Lightning
> Message-ID:
> <CALL-=e5mF9TqbbD=
> Cf-bawbw4dq2PGjC9W_nqAQeHsB829ZpNg at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> 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
> >
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://lists.linuxfoundation.org/pipermail/lightning-dev/attachments/20211206/f3253ec4/attachment-0001.html
> >
>
> ------------------------------
>
> Message: 2
> Date: Mon, 6 Dec 2021 12:31:29 +0100
> From: Martin Habov?tiak <martin.habovstiak at gmail.com>
> To: Karl <gmkarl at gmail.com>
> Cc: Bitcoin Protocol Discussion
> <bitcoin-dev at lists.linuxfoundation.org>, lightning-dev
> <lightning-dev at lists.linuxfoundation.org>, H?ctor Jos? C?rdenas
> Pacheco <hcarpach at gmail.com>
> Subject: Re: [Lightning-dev] [bitcoin-dev] Sending OP_RETURN via
> Bitcoin Lightning
> Message-ID:
> <
> CALkkCJas_pf7Un45CJyFg8j9cBk8PtKN4iYAL81TtLSRNnKqeg at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> 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/lightning-dev/attachments/20211206/d86e56cb/attachment-0001.html
> >
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> Lightning-dev mailing list
> Lightning-dev at lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/lightning-dev
>
>
> ------------------------------
>
> End of Lightning-dev Digest, Vol 76, Issue 4
> ********************************************
>
--
~ John Carvalho
Schedule: https://calendly.com/bitcoinerrorlog
Chat: https://t.me/bitcoinerrorlog
Social: https://twitter.com/bitcoinerrorlog
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/lightning-dev/attachments/20211206/e4816d2d/attachment.html>;