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"
Subject: [bitcoin-dev] TARO Protocol metadata BIP proposal
Precedence: list

--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 &quot;ticker&quot;: // [optional] Fung=
ible assets should have ticker=C2=A0<br>=C2=A0 =C2=A0 &quot;type&quot;: // =
Stablecoin | Image | Video | Data ... Type of the asset<br>=C2=A0 =C2=A0 &q=
uot;description&quot;: // [mandatory] Short description of the asset explai=
ning how the asset works<br>=C2=A0 =C2=A0 &quot;data&quot;: // [optional] B=
ase64 formatted image data. This is the image representation of the asset /=
 an icon representing the asset.<br>=C2=A0 =C2=A0 &quot;hash_data&quot;: //=
 [optional] Hash of the data that asset represents<br>=C2=A0 =C2=A0 &quot;e=
xternal_url&quot;: // [optional] External URL to the thing that the asset r=
epresents<br>=C2=A0 =C2=A0 &quot;attributes&quot;: { // [optional] External=
 URL to the thing that the asset represents<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =
&quot;collection_name&quot;:=C2=A0<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 ...<br>=
=C2=A0 =C2=A0 }=C2=A0<br>=C2=A0 =C2=A0 &quot;minter_info&quot;: { // [optio=
nal] Information about the entity that minted the asset<br>=C2=A0 =C2=A0 =
=C2=A0 =C2=A0 &quot;name&quot;:<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 &quot;email&=
quot;:<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 &quot;phone&quot;:<br>=C2=A0 =C2=A0 =
=C2=A0 =C2=A0 &quot;telegram&quot;:<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 &quot;we=
bsite&quot;:<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--