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
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
|
Return-Path: <adam@tiramisuwallet.com>
Received: from smtp4.osuosl.org (smtp4.osuosl.org [140.211.166.137])
by lists.linuxfoundation.org (Postfix) with ESMTP id 12CFDC002A
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 21 Apr 2023 09:47:12 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by smtp4.osuosl.org (Postfix) with ESMTP id D55484288B
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 21 Apr 2023 09:47:11 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp4.osuosl.org D55484288B
Authentication-Results: smtp4.osuosl.org;
dkim=pass (2048-bit key) header.d=tiramisuwallet-com.20221208.gappssmtp.com
header.i=@tiramisuwallet-com.20221208.gappssmtp.com header.a=rsa-sha256
header.s=20221208 header.b=lkweRlEa
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -1.098
X-Spam-Level:
X-Spam-Status: No, score=-1.098 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
FROM_FMBLA_NEWDOM28=0.799, HTML_MESSAGE=0.001,
RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001]
autolearn=no autolearn_force=no
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 gra0z7BaLM5o
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 21 Apr 2023 09:47:09 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.8.0
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp4.osuosl.org 102F042884
Received: from mail-wm1-x333.google.com (mail-wm1-x333.google.com
[IPv6:2a00:1450:4864:20::333])
by smtp4.osuosl.org (Postfix) with ESMTPS id 102F042884
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 21 Apr 2023 09:47:06 +0000 (UTC)
Received: by mail-wm1-x333.google.com with SMTP id
5b1f17b1804b1-3f176a16c03so9982025e9.2
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 21 Apr 2023 02:47:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=tiramisuwallet-com.20221208.gappssmtp.com; s=20221208; t=1682070425;
x=1684662425;
h=to:subject:message-id:date:from:mime-version:from:to:cc:subject
:date:message-id:reply-to;
bh=k+GketKi8BoR8S2uu+kzAbjfr0HsSLr56Cc/nB4VMmw=;
b=lkweRlEaQICkvLDqFjXYi4atRTUF9A1sOnxTmyl5D4RmE4D+b6Oq07m4bzGwAIO1F4
Od7iUumIWiEDTtSMHmAldErCxeclHqD1CvROLCfk/Lr454TUR9WDZiblaAB4YzyHtv6/
5GgPnPgOUuSJbj8muHKwlzXM9pvdH1Fk2eyvjUTDmZZIEmz07pV+E86evp7SitAbtclo
PpvU5bmFQtTmTavWQVQjcY0x4PaVCnbhDGKPOgv7i8vP+U3yVJ0H6gYKKBxHS4v1KylV
1TfoLthZOkvR3kqzbj0KOd8SNBNNZ4Ke8hwxtsown8GYm1CLL3P2evuU4apoBVZaUvaZ
q1Ug==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20221208; t=1682070425; x=1684662425;
h=to:subject:message-id:date:from:mime-version:x-gm-message-state
:from:to:cc:subject:date:message-id:reply-to;
bh=k+GketKi8BoR8S2uu+kzAbjfr0HsSLr56Cc/nB4VMmw=;
b=hCgplBCMspQNkkSkdrY2+eJyTEDgfDC+V5eckW1DmlanLwBiD7QKDUjJXg7fUVnicG
7PdcSuUpizdO7s2Qn1cVc4I/AReWUCslwQvm3apaQdgx6btsrrHaR1NXxMe0zMxbETfk
Y1+vAPA/0b5DH/plHy1gA8vt3W1AtgQzObwz3e3vMUVNnDwle8Ho4UllOcMTnFRA7fB2
CDtuuVZZjzfCywLhndq8xGAysHF/I4JaCeO/iBtMD4B89N7K+hjH6k/ecP8iX7UXvEUy
xnHUe6ybzr35ykFAZITucH5943W10blFMUVL0HnwC89UN5NWq3gGANjhE5+QKKsoL55b
Wq4g==
X-Gm-Message-State: AAQBX9cDtqAUKqCM2LWhgh4R0lJdGXPnI/t9h4FYmzStMqlev4AHqdfm
VjjSGi5X9jZPbzceL3XhSupT2F8HEEJV5cBw1ix72aRq/v/Jdoa7u6Lcqg==
X-Google-Smtp-Source: AKy350aeO0WC9JRH8zuCg7gkxnnHGHD1BwL1fqPIIs0iA0f/UN6cyWO4uhGoh/p3orL2JExs6GZTupKAu4/9EDzyB1E=
X-Received: by 2002:a7b:ce87:0:b0:3f1:7277:eaa with SMTP id
q7-20020a7bce87000000b003f172770eaamr1393485wmj.31.1682070424599; Fri, 21 Apr
2023 02:47:04 -0700 (PDT)
MIME-Version: 1.0
From: Adam Ivansky <adam@tiramisuwallet.com>
Date: Fri, 21 Apr 2023 05:46:53 -0400
Message-ID: <CACxPPdiSqT5BC28MW1-3F7U+jf3s1N6ojCTaAMJQMACqhQ-=0w@mail.gmail.com>
To: bitcoin-dev@lists.linuxfoundation.org
Content-Type: multipart/alternative; boundary="0000000000002550cb05f9d58aa1"
X-Mailman-Approved-At: Fri, 21 Apr 2023 17:12:19 +0000
Subject: [bitcoin-dev] TARO Protocol metadata BIP proposal
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: Fri, 21 Apr 2023 09:47:12 -0000
--0000000000002550cb05f9d58aa1
Content-Type: text/plain; charset="UTF-8"
Hi all / happy Friday ,
I would like to propose a BIP for the metadata structure of assets traded
on TARO Protocol running on Bitcoin blockchain. A new bip-taro.mediawiki
file.
The BIP for TARO is here
https://github.com/Roasbeef/bips/blob/bip-taro/bip-taro.mediawiki . TARO
BIP does not explicitly talk about the format of metadata of the assets.
However this is something we will have to agree on if we are to start
trading NFTs, Stablecoins and different synthetic assets such as tokenized
stocks / options.
For the past few months I have been operating a wallet for TARO called
Tiramisu Wallet on testnet ( https://testnet.tarowallet.net/ ) and I was
able to put together a list of fields that the metadata should have . This
is a result of myself testing different use cases for the protocol as well
as external users coming in and minting different assets.
My observation is that users care a lot about the ticker, asset name,
description, image representing the asset, info on who minted the asset.
For this reason I would like to propose a BIP for TARO Protocol asset
metadata. I think this should be separate from the TARO BIP as the format
of asset metadata might evolve depending on the real-life use cases and
what assets end up being minted / traded on TARO.
I am proposing that the metadata is structured as a JSON stored as a string
and that it is formatted as follows:
{
"ticker": // [optional] Fungible assets should have ticker
"type": // Stablecoin | Image | Video | Data ... Type of the asset
"description": // [mandatory] Short description of the asset explaining
how the asset works
"data": // [optional] Base64 formatted image data. This is the image
representation of the asset / an icon representing the asset.
"hash_data": // [optional] Hash of the data that asset represents
"external_url": // [optional] External URL to the thing that the asset
represents
"attributes": { // [optional] External URL to the thing that the asset
represents
"collection_name":
...
}
"minter_info": { // [optional] Information about the entity that minted
the asset
"name":
"email":
"phone":
"telegram":
"website":
}
}
This was loosely inspired by the standard use by OpenSea
https://docs.opensea.io/docs/metadata-standards only in case of TARO we
have less of an incentive to make the metadata small as this data is not
written to blockchain directly.
This is why I think we should start including the actual image data into
the metadata.
Tiramisu wallet is on testnet right now and uses some of these JSON fields.
Please let me know how you feel about this.
PS: I am following the manual from here
https://github.com/Roasbeef/bips/tree/bip-taro that says my first step
should be sending an email to this mailing list .
Best regards,
Adam Ivansky
Founder of Tiramisu Wallet
--0000000000002550cb05f9d58aa1
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">Hi all / happy Friday ,<div><br></div><div>I would like to=
propose a BIP for the metadata structure of assets traded on TARO Protocol=
running on Bitcoin blockchain. A new=C2=A0bip-taro.mediawiki file.</div><d=
iv><br></div><div>The BIP for TARO is here=C2=A0<a href=3D"https://github.c=
om/Roasbeef/bips/blob/bip-taro/bip-taro.mediawiki" target=3D"_blank">https:=
//github.com/Roasbeef/bips/blob/bip-taro/bip-taro.mediawiki</a>=C2=A0. TARO=
BIP does not explicitly=C2=A0talk about the format of metadata of the asse=
ts. However this is something we will have to agree on if we are to start t=
rading NFTs, Stablecoins and different synthetic assets such as tokenized s=
tocks / options.</div><div><br></div><div>For the past few months I have be=
en operating a wallet for TARO called Tiramisu Wallet on testnet (=C2=A0<a =
href=3D"https://testnet.tarowallet.net/" target=3D"_blank">https://testnet.=
tarowallet.net/</a>=C2=A0) and I was able to put together a list of fields =
that the metadata should have . This is a result of myself testing differen=
t use cases for the protocol as well as external users=C2=A0coming=C2=A0in =
and minting different assets.</div><div><br></div><div>My observation is th=
at users care a lot about the ticker, asset name, description, image repres=
enting=C2=A0the asset, info on who minted the asset.=C2=A0</div><div><br></=
div><div>For this reason I would like to propose a BIP for TARO Protocol as=
set metadata. I think this should be separate from the TARO BIP as the form=
at of asset metadata might evolve depending on the real-life use cases and =
what assets end up being minted / traded on TARO.</div><div><br></div><div>=
I am proposing that the metadata is structured as a JSON stored as a string=
and that it is formatted=C2=A0as follows:</div><div><br></div><div><font f=
ace=3D"monospace">{<br>=C2=A0 =C2=A0 "ticker": // [optional] Fung=
ible assets should have ticker=C2=A0<br>=C2=A0 =C2=A0 "type": // =
Stablecoin | Image | Video | Data ... Type of the asset<br>=C2=A0 =C2=A0 &q=
uot;description": // [mandatory] Short description of the asset explai=
ning how the asset works<br>=C2=A0 =C2=A0 "data": // [optional] B=
ase64 formatted image data. This is the image representation of the asset /=
an icon representing the asset.<br>=C2=A0 =C2=A0 "hash_data": //=
[optional] Hash of the data that asset represents<br>=C2=A0 =C2=A0 "e=
xternal_url": // [optional] External URL to the thing that the asset r=
epresents<br>=C2=A0 =C2=A0 "attributes": { // [optional] External=
URL to the thing that the asset represents<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =
"collection_name":=C2=A0<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 ...<br>=
=C2=A0 =C2=A0 }=C2=A0<br>=C2=A0 =C2=A0 "minter_info": { // [optio=
nal] Information about the entity that minted the asset<br>=C2=A0 =C2=A0 =
=C2=A0 =C2=A0 "name":<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 "email&=
quot;:<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 "phone":<br>=C2=A0 =C2=A0 =
=C2=A0 =C2=A0 "telegram":<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 "we=
bsite":<br>=C2=A0 =C2=A0 }<br>}</font><br></div><div><br></div><div>Th=
is was loosely inspired by the standard use by OpenSea=C2=A0<a href=3D"http=
s://docs.opensea.io/docs/metadata-standards" target=3D"_blank">https://docs=
.opensea.io/docs/metadata-standards</a>=C2=A0only in case of TARO we have l=
ess of an incentive to make the metadata small as this data is not written =
to blockchain directly.</div><div>This is why I think we should start inclu=
ding the actual image data into the metadata.</div><div><br></div><div>Tira=
misu wallet is on testnet right now and uses some of these JSON fields.=C2=
=A0</div><div><br></div><div>Please let me know how you feel about this.</d=
iv><div><br></div><div>PS: I am following the manual from here=C2=A0<a href=
=3D"https://github.com/Roasbeef/bips/tree/bip-taro" target=3D"_blank">https=
://github.com/Roasbeef/bips/tree/bip-taro</a>=C2=A0that says my first step =
should be sending=C2=A0an email to this mailing list .</div><div><br></div>=
<div>Best regards,</div><div><br></div><div>Adam Ivansky</div><div><br></di=
v><div>Founder of Tiramisu Wallet</div></div>
--0000000000002550cb05f9d58aa1--
|
