Skip to content

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

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 4 commits into
base: master
Choose a base branch
from
Open

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

Changes from 1 commit
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
eeafdcf
Update 0064-token-data-standard.md
Gusarich Sep 23, 2023
c805199
Update 0064-token-data-standard.md
Gusarich Sep 23, 2023
2a460eb
Update 0064-token-data-standard.md
Gusarich Sep 23, 2023
7b5655f
Update 0064-token-data-standard.md
Gusarich Sep 23, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Next Next commit
Update 0064-token-data-standard.md
  • Loading branch information
@Gusarich
Gusarich authored Sep 23, 2023
commit eeafdcff1c74340d827e3985e75e81af82350253
13 changes: 9 additions & 4 deletions text/0064-token-data-standard.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@ For applications like wallets or marketplaces it is quite useful to be able auto

# Guide

Each token (and also NFT Collection) has its own metadata. It contains some info about token, such as title and associated image. Metadata can be stored offchain (smart contract will contain only a link to json) or onchain (all data will be stored in smart contract).
Each token (and also NFT Collection) has its own metadata. It contains some info about token, such as title and associated image. Metadata can be stored offchain (smart contract will contain only a link to json), onchain (all data will be stored in smart contract), or in TON Storage (smart contract will contain only a bag id of a json).

## NFT Collection metadata example (offchain)

Expand Down Expand Up @@ -78,10 +78,15 @@ Three options can be used:
The first byte is `0x00` and the rest is key/value dictionary.
Key is sha256 hash of string.
Value is data encoded as described in "Data serialization" paragraph.
3. **Semi-chain content layout**
3. **TON Storage content layout**
The first byte is `0x02` and the rest is the Bag ID pointing to the JSON document containing the token metadata. Bag ID is stored as a regular 256-bit integer.
4. **Semi-chain content layout**
Data encoded as described in "2. On-chain content layout".
The dictionary must have `uri` key with a value containing the URI pointing to the JSON document with token metadata.
Clients in this case should merge the keys of the on-chain dictionary and off-chain JSON doc.
1. **Off-chain continuation**
The dictionary must have `uri` key with a value containing the URI pointing to the JSON document with token metadata.
Clients in this case should merge the keys of the on-chain dictionary and off-chain JSON doc.
2. **TON Storage continuation**
The idea is same as in **4.1** but the key is `bagid` and the value is an integer value of Bag ID.

## Data serialization
Data that does not fit in one cell can be stored in two ways:
Expand Down