From: Andrew Melnychuk Oseen <amo.personal@protonmail•com>
To: Adam Ivansky <adam@tiramisuwallet•com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] TARO Protocol metadata BIP proposal
Date: Wed, 26 Apr 2023 22:11:36 +0000 [thread overview]
Message-ID: <lgDB6aSdKZZKAL7Ccx-9CUMDpxDecUDFhAtnCqsUho2YDG6TSgRtSw2relSfyRgpmfwuZPbCIbVx7dZxB9Gg6FOnYOkb_Fqfgtguw21L_-4=@protonmail.com> (raw)
In-Reply-To: <CACxPPdiSqT5BC28MW1-3F7U+jf3s1N6ojCTaAMJQMACqhQ-=0w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3247 bytes --]
Big fan of this. I don't have the technical expertise to suggest much, but I think that is a really good start for a foundation of bearer instruments.
-Andrew
Sent with [Proton Mail](https://proton.me/) secure email.
------- Original Message -------
On Friday, April 21st, 2023 at 2:46 AM, Adam Ivansky via bitcoin-dev <bitcoin-dev@lists•linuxfoundation.org> wrote:
> 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
[-- Attachment #2: Type: text/html, Size: 5064 bytes --]
prev parent reply other threads:[~2023-04-26 22:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-21 9:46 Adam Ivansky
2023-04-26 22:11 ` Andrew Melnychuk Oseen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='lgDB6aSdKZZKAL7Ccx-9CUMDpxDecUDFhAtnCqsUho2YDG6TSgRtSw2relSfyRgpmfwuZPbCIbVx7dZxB9Gg6FOnYOkb_Fqfgtguw21L_-4=@protonmail.com' \
--to=amo.personal@protonmail$(echo .)com \
--cc=adam@tiramisuwallet$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox