Add standard for mintless jettons #177
Conversation
|
|
||
| This standard propose to use `custom_payload` to store there _claim airdrop_ command with the following scheme: | ||
| ``` | ||
| merkle_airdrop_claim proof:^Cell = CustomPayload; |
There was a problem hiding this comment.
merkle_airdrop_claim#0df602d6 proof:^Cell = CustomPayload;
There was a problem hiding this comment.
من گیج دم چی ب چیه اصلا قاطی کردم
|
|
||
| Method `is_minted()` for jetton wallets returns `bool` whether jetton is minted or not. | ||
|
|
||
| //TODO: make better naming |
There was a problem hiding this comment.
As we discussed with with mr-tron instead of get_method lets move custom_payload source to metadata. This will not cause security issue (owner silently changes metadata) since Merkle root checks are done in contracts and root won't be changed.
I propose to have:
custom_payload_augmentation_endpoint with some specified scheme (like cNFT)
and custom_payload_augmentation_hashmap can be link to web2, tonstorage, ipfs ...
EmelyanenkoK
changed the title
| ### | ||
|
|
||
| In metadate stored according to [Metadata standard](https://github.com/ton-blockchain/TEPs/blob/master/text/0064-token-data-standard.md) | ||
| should be added field "mintles_merkle_dump_uri" with `string` type in json or `ContentData` type in TL-B: |
| ### Useful links | ||
|
|
||
| 1. [Reference contract implementation](https://github.com/ton-community/mintless-jetton) | ||
| 2. [Custom payload API](ttps://github.com/ton-blockchain/TEPs/blob/master/text/0000-jetton-offchain-payloads.md) |
There was a problem hiding this comment.
EQCDjUcZdVCmk7myvIuZqJ7WGC1UW0845XE2rmCPKkGWiVDO
There was a problem hiding this comment.
Thank you, I will use it to solve the problem of receiving jettons
| In metadate stored according to [Metadata standard](https://github.com/ton-blockchain/TEPs/blob/master/text/0064-token-data-standard.md) | ||
| should be added field "mintles_merkle_dump_uri" with `string` type in json or `ContentData` type in TL-B: | ||
|
|
||
| `mintles_merkle_dump_uri` pointed to binary file contains BoC with merkle tree of all jettons wallets. |
There was a problem hiding this comment.
I'm sure that mintless (double s) should be there
| = InternalMsgBody; | ||
| ``` | ||
|
|
||
| This standard propose to use `custom_payload` to store there _claim airdrop_ command with the following scheme: |
|
|
||
| ## GetMethods | ||
|
|
||
| Method `is_claimed()` for jetton wallets returns `bool` whether jetton is minted or not. |
There was a problem hiding this comment.
My problem is to transfer the verified token from tonviewer, there is no option to change or transfer to the main account
|
Also I see that the document doesn't explicitly state what happens if the airdrop claim conditions are not met (e.g., if it's already claimed or outside the time window). It might be helpful to specify the expected behavior in these cases. |
|
|
||
| ### Custom payload and indexation API | ||
|
|
||
| Described in [Jetton Offchain Payloads](https://github.com/ton-blockchain/TEPs/blob/master/text/0000-jetton-offchain-payloads.md) TEP. |
|
|
||
| ### | ||
|
|
||
| In metadate stored according to [Metadata standard](https://github.com/ton-blockchain/TEPs/blob/master/text/0064-token-data-standard.md) |
| ### Custom payload and indexation API | ||
|
|
||
| Described in [Jetton Offchain Payloads](https://github.com/ton-blockchain/TEPs/blob/master/text/0000-jetton-offchain-payloads.md) TEP. | ||
|
|
||
| ### GetMethods |
There was a problem hiding this comment.
text/0000-compressed-jetton-standard.md
No description provided.