Update TEP-64 with the TON Storage method for storing token data

[Gusarich]

As The Open Network continues its growth in Web3 direction, the relevance of TON Storage is intensifying. It has become imperative to standardize the method of storing token metadata within TON Storage.

This Pull Request introduces a new approach to metadata storage using TON Storage. Additionally, it enhances the existing Semi-chain content layout by offering the ability to store supplementary data using TON Storage.

[howardpen9]

nice

[tvorogme]

Hey, let's add:

• "website"
• "social"

Keys to on-chain data? Those tags usually used by collections & jetton owners. Both keys must contain string value of URL

Or we can think about dict where key will be index of link, and value link. To allow several links per 1 item

[EmelyanenkoK]

Do we need additional path parameter in tonstorage#02 for bags with more than 1 file?

[mr-tron]

why binary encoding is better than simple OffChain url "tonstorage://BAGBAGID/token.json"? Url is already supported by different services like tonkeeper/tonapi/tonviewer and maybe some others.

[Gusarich]

Hey, let's add:

• "website"
• "social"

Keys to on-chain data? Those tags usually used by collections & jetton owners. Both keys must contain string value of URL

Or we can think about dict where key will be index of link, and value link. To allow several links per 1 item

Hey @tvorogme! It may be useful to expand the standard for metadata attributes, but I think it's out of scope of this PR.

[Gusarich]

Do we need additional path parameter in tonstorage#02 for bags with more than 1 file?

@EmelyanenkoK useful remark! We need it for sure. I guess that simple Maybe Text field will be enough?

tonstorage#02 bagid:uint256 path:(Maybe Text) = FullContent;

[Gusarich]

why binary encoding is better than simple OffChain url "tonstorage://BAGBAGID/token.json"? Url is already supported by different services like tonkeeper/tonapi/tonviewer and maybe some others.

@mr-tron Well, maybe it's enough. But anyway, we need to standardise it in the TEP.

[mr-tron]

Ok. You can write in standard what meta url should have schema from list http|https|tonstorage|ipfs|ipns ~~ftp~~ ohshit