1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
|
Return-Path: <hcarpach@gmail.com>
Received: from smtp4.osuosl.org (smtp4.osuosl.org [140.211.166.137])
by lists.linuxfoundation.org (Postfix) with ESMTP id 049DDC0012;
Mon, 6 Dec 2021 09:54:36 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by smtp4.osuosl.org (Postfix) with ESMTP id D2A7A40144;
Mon, 6 Dec 2021 09:54:35 +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 JBdEeNSst553; Mon, 6 Dec 2021 09:54:34 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.8.0
X-Greylist: whitelisted by SQLgrey-1.8.0
Received: from mail-ua1-x933.google.com (mail-ua1-x933.google.com
[IPv6:2607:f8b0:4864:20::933])
by smtp4.osuosl.org (Postfix) with ESMTPS id 7F8CC40142;
Mon, 6 Dec 2021 09:54:34 +0000 (UTC)
Received: by mail-ua1-x933.google.com with SMTP id ay21so18279628uab.12;
Mon, 06 Dec 2021 01:54:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112;
h=from:mime-version:subject:message-id:date:cc:to;
bh=f1F5jN4RB0eDrl5MIQrZ0nc11H4xkoPh5X1WndrgxPA=;
b=f6lKsLEWynFk5eie+HYWQc0xDb6YcF9tsRwvMFM8auiZGSbdY2SKQsao+KtsoLEGsQ
ah7thtGlws2DiRzUscbwFQX31h4rvFfDkImDr1VOmFYfOSuDiqGbgN5/eU+qBQ3l9z8g
8sJzhp/Lch40ToaCveGl0W/4tNyrhVkB6701DOKIjZ7KN/8yzYOKnUkrF1I+ChH2PLaf
oVgLqYcv4gCVwInOmr2wP/a751xNm9LLwABw22vFO6Ox/ODjV+dE8Q/jyhlmugMcV4En
p46orxCypDn7x0ISKOXlMXuWaz10TGiZf6tb3QiyvU1V3gLrUA9+1QULKW/2p1m0rCKl
W4Bw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20210112;
h=x-gm-message-state:from:mime-version:subject:message-id:date:cc:to;
bh=f1F5jN4RB0eDrl5MIQrZ0nc11H4xkoPh5X1WndrgxPA=;
b=h6qHZe8WYSU30dSCCMWignFj7enU060J+W/WSflyz4XKTRe4qPHk1Sb3YHb3UvkikQ
3xAi29pmuQoB9sRk0WLLJPTnXmjaveDLRe60DWp5eIewSNnTkkajEtZcSeVRB3hXs9NF
TDhzAeaYKXN5ZICXQ+Ud3UcnDxJ4RHVf60HrflkN4DY4H+lunvGBDxtLMfkR4FM4H52R
6nquGAri5m73JM1yLg7Yk62RZkK3hO6s7HbHda1gGmfK0KXj47lSU5fTnYLuo+iyTjr0
CpOkmrZEFSsJ9UCvBE5zIx8/ZIv3YxRX0WBSGHexV2civob/UfDQlM2dQBugDeTvbRsu
lWWA==
X-Gm-Message-State: AOAM531tZsEOBpuaD2Y5Jbd+nwoWfWoqqzg8Bdo+IaZ0OoZMLMzHhKIV
DBy76dmYOLMU5BtcAYH6GEpUrS3lYW8=
X-Google-Smtp-Source: ABdhPJxF39Io+Q6fM3gpU88rp2bZGGyP08LADcpZc2Cs/Wt+izJmzSN33u5G5TN4/Nhq7IXDzy663w==
X-Received: by 2002:a05:6102:e46:: with SMTP id
p6mr35673667vst.33.1638784473050;
Mon, 06 Dec 2021 01:54:33 -0800 (PST)
Received: from smtpclient.apple ([2800:810:446:fe3:cc5d:a02c:746f:7e01])
by smtp.gmail.com with ESMTPSA id b11sm3757621vsp.6.2021.12.06.01.54.31
(version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128);
Mon, 06 Dec 2021 01:54:32 -0800 (PST)
From: =?utf-8?Q?H=C3=A9ctor_Jos=C3=A9_C=C3=A1rdenas_Pacheco?=
<hcarpach@gmail.com>
Content-Type: multipart/alternative;
boundary="Apple-Mail=_F62FC61C-752D-4A62-95EE-9119E61B8378"
Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.20.0.1.32\))
Message-Id: <DD7D5A8B-F61F-4302-ACF4-CE731843D97D@gmail.com>
Date: Mon, 6 Dec 2021 06:54:30 -0300
To: bitcoin-dev@lists.linuxfoundation.org
X-Mailer: Apple Mail (2.3693.20.0.1.32)
X-Mailman-Approved-At: Mon, 06 Dec 2021 10:04:53 +0000
Cc: lightning-dev@lists.linuxfoundation.org
Subject: [bitcoin-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 <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Dec 2021 09:54:36 -0000
--Apple-Mail=_F62FC61C-752D-4A62-95EE-9119E61B8378
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=utf-8
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 other new ones) and =
was wondering if it=E2=80=99s possible to make transactions with this =
opcode via Lightning.
More specific questions could be:
Can opcodes like OP_RETURN be inside a channel=E2=80=99s 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=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
--Apple-Mail=_F62FC61C-752D-4A62-95EE-9119E61B8378
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
charset=utf-8
<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D""><div =
dir=3D"auto" style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
line-break: after-white-space;" class=3D""><div dir=3D"auto" =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; line-break: =
after-white-space;" class=3D""><div dir=3D"auto" style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" =
class=3D"">Hello all,<div class=3D""><br class=3D""></div><div =
class=3D"">I=E2=80=99ve 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=E2=80=99s possible to make transactions =
with this opcode via Lightning.</div><div class=3D""><br =
class=3D""></div><div class=3D"">More specific questions could =
be:</div><div class=3D""><ol class=3D""><li class=3D"">Can opcodes like =
OP_RETURN be inside a channel=E2=80=99s opening or closing =
transaction?</li><li class=3D"">If so, could that OP_RETURN change hands =
within that channel or network of channels?</li><li class=3D"">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?</li></ol></div><div class=3D"">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.</div><div =
class=3D""><br class=3D""></div><div class=3D"">Thank in =
advance.</div></div><div class=3D"">
<meta charset=3D"UTF-8" class=3D""><div>=E2=80=94=E2=80=94<br =
class=3D""><b class=3D"">H=C3=A9ctor C=C3=A1rdenas<br =
class=3D""></b>@hcarpach</div>
</div>
<br class=3D""></div></div></body></html>=
--Apple-Mail=_F62FC61C-752D-4A62-95EE-9119E61B8378--
|
