Return-Path: Received: from smtp4.osuosl.org (smtp4.osuosl.org [IPv6:2605:bc80:3010::137]) by lists.linuxfoundation.org (Postfix) with ESMTP id A052CC0012; Mon, 6 Dec 2021 11:31:43 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp4.osuosl.org (Postfix) with ESMTP id 96183408CE; Mon, 6 Dec 2021 11:31:43 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org X-Spam-Flag: NO X-Spam-Score: -2.098 X-Spam-Level: X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: smtp4.osuosl.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from smtp4.osuosl.org ([127.0.0.1]) by localhost (smtp4.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zAVhP5puBBQd; Mon, 6 Dec 2021 11:31:42 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.8.0 X-Greylist: whitelisted by SQLgrey-1.8.0 Received: from mail-io1-xd30.google.com (mail-io1-xd30.google.com [IPv6:2607:f8b0:4864:20::d30]) by smtp4.osuosl.org (Postfix) with ESMTPS id 8B9A6408CB; Mon, 6 Dec 2021 11:31:42 +0000 (UTC) Received: by mail-io1-xd30.google.com with SMTP id q72so7838805iod.12; Mon, 06 Dec 2021 03:31:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=aM1Bi4bWeQ06UxPGDkaOsbZdrOvZ1vMpq+SPgkEAdvY=; b=Qk5HmR92zALVecQgk3yrxVJEbOYX2RGjXwyAcg5q2TWz/Nixw9UoazUwJwtWTRcqxn P22qy+ogyspxL7chw0MMSF6F7zvgcJARE8B3nigeD3fEPDn2qrWmGa0lHeerp29TYNK8 sfZyUmeYEY7JrL9UPzcQC24DLaO2u7NOrzBhr4isG+58jvRE+fV6s/IAjK/94wGIER3H 9L2vt7spc4ahkO6jbY6CWGx5lX/3KDuaIiPY29O0sae4x6J5GMCN03Z8+MhYdbVhzM5M aU4bdEGHmyvCriBovhsfRbnaG5W3VMm55pw8OwY/CgylvXRjXoDEdQSWmmCKA2+ZP309 ub3w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=aM1Bi4bWeQ06UxPGDkaOsbZdrOvZ1vMpq+SPgkEAdvY=; b=kCA0UHvZAqwRlx3v8s1qzQF0aPlQTwfvJ2tDPV9YloCueROLzH6CwJgMPNSu7ZntEK c9w6nHFZp84Uepcx9OSZTrdtP+mL17Y+cn6tztljAQ0vDQ+OcISHwCz1/5aWXz5FahI2 rCmaaMzo9D0u3rIGYov4lNvxXbJsMvFmxysfSOL+jCYJwggdeFJZzHljKzoCPVtAvyFi Co77hQ0zhfO7T2WVBmjiwxsT5Mb0Ck1aO13o7pwoclmM5xREtCoJOdaKJYBCYSZ57ct8 l3UL262URdOUePPxz1fbyyPi0gDsUUPA9Ic7Tu/OBluCEt8kok3tiJfCzOtxxJ5+yK/d N7lQ== X-Gm-Message-State: AOAM5331PE961uT0UM3Tb40y9HCXhBxFlRIMics3zlYpr1KklvprzUEc /nszEkcDbGZmC7pHd/BiGHuSExzXgZ/Ky70aeKU= X-Google-Smtp-Source: ABdhPJwWNVXQR6bjPX1nkTdNphwFCU1feWQdCLkCNyjbNynZJ8h2yEU8LBVwWMUrVFN3t6AxQykcoS0ObH0ie4MiRQA= X-Received: by 2002:a05:6638:dd5:: with SMTP id m21mr40028002jaj.44.1638790300841; Mon, 06 Dec 2021 03:31:40 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: =?UTF-8?Q?Martin_Habov=C5=A1tiak?= Date: Mon, 6 Dec 2021 12:31:29 +0100 Message-ID: To: Karl Content-Type: multipart/alternative; boundary="000000000000be38f005d2789958" X-Mailman-Approved-At: Mon, 06 Dec 2021 15:43:52 +0000 Cc: Bitcoin Protocol Discussion , lightning-dev , =?UTF-8?Q?H=C3=A9ctor_Jos=C3=A9_C=C3=A1rdenas_Pacheco?= Subject: Re: [bitcoin-dev] [Lightning-dev] Sending OP_RETURN via Bitcoin Lightning X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Bitcoin Protocol Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Dec 2021 11:31:43 -0000 --000000000000be38f005d2789958 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable I recommend you researching RGB: https://rgb-org.github.io/ On Mon, Dec 6, 2021, 11:21 Karl wrote: > Hi, > > I'm not a bitcoin developer. > > On Mon, Dec 6, 2021, 5:05 AM H=C3=A9ctor Jos=C3=A9 C=C3=A1rdenas Pacheco = via bitcoin-dev < > bitcoin-dev@lists.linuxfoundation.org> wrote: > >> Hello all, >> >> I=E2=80=99ve been thinking about how OP_RETURN is being used to create a= nd trade >> NFTs on Bitcoin (think RarePepes, SoG and other new ones) and was wonder= ing >> if it=E2=80=99s 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=E2=80=99s opening o= r >> 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 i= s > not hard to define a protocol that associates an OP_RETURN with ownership= , > and ownership could then be transferred via lightning by sending associat= ed > 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 pri= mary >> 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=E2=80=99m 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. >> =E2=80=94=E2=80=94 >> >> *H=C3=A9ctor C=C3=A1rdenas*@hcarpach >> >> _______________________________________________ >> bitcoin-dev mailing list >> bitcoin-dev@lists.linuxfoundation.org >> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev >> > _______________________________________________ > Lightning-dev mailing list > Lightning-dev@lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/lightning-dev > --000000000000be38f005d2789958 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I recommend you researching RGB:=C2=A0https://rgb-org.github.io/

On Mon, Dec 6, 2021, 11:2= 1 Karl <gmkarl@gmail.com> wro= te:
Hi,

I'm not a bitcoin develo= per.

On Mon, Dec 6, 2021, 5:05 AM H=C3=A9ctor Jos=C3=A9 C=C3=A1r= denas Pacheco via bitcoin-dev <bitcoin-dev@lists.linu= xfoundation.org> wrote:
Hello= all,

I=E2=80=99ve been thinking about how OP_RETURN is = being used to create and trade NFTs on Bitcoin (think RarePepes, SoG and ot= her new ones) and was wondering if it=E2=80=99s 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=E2=80=99s opening or closing tr= ansaction?
  2. If so, could that OP_RETURN change hands within that cha= nnel or network of channels?
OP_RETURNs do not have ownership accord= ing to the bitcoin network.=C2=A0 It is not hard to define a protocol that = associates an OP_RETURN with ownership, and ownership could then be transfe= rred via lightning by sending associated currency via lightning.=C2=A0 Robu= stness improvements seem possible.

=
  1. If possible, could the OP_RETURN be divisible? Could one person sen= d a piece of a OP_RETURN just like one can do right now on the primary ledg= er or would it need to maintain the OP_RETURN code intact?
<= /div>
OP_RETURN= s themselves do not have ownership, but you can define a protocol that give= s them divisible ownership, including via lightning.

I=E2=80=99m assuming that, if possible, this would need a= protocol layer parallel to Bitcoin/Lightning that stores and reads all Bit= coin transactions and the ones which involve the node's channels as wel= l as the ones with the OP_RETURN, just like CounterParty does right now wit= h the primary ledger.

Thank in advance.
=E2=80=94=E2=80=94
H=C3=A9ctor C=C3=A1rdenas
@hcarpach

_______________________________________________
bitcoin-dev mailing list
bitcoin-dev@lists.linuxfoundation.org
https://lists.li= nuxfoundation.org/mailman/listinfo/bitcoin-dev
_______________________________________________
Lightning-dev mailing list
Lightning-dev@lists.linuxfoundation.org
https://lists.linuxfounda= tion.org/mailman/listinfo/lightning-dev
--000000000000be38f005d2789958--