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 ...
| ### | ||
|
|
||
| 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
| 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. |
|
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. |
Ami22r
left a comment
There was a problem hiding this comment.
EQCDjUcZdVCmk7myvIuZqJ7WGC1UW0845XE2rmCPKkGWiVDO
AkiraMatthew
left a comment
There was a problem hiding this comment.
I think the Mintless feature should be better described for non-TON devs to understand better how it works
|
|
||
| ### 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) |
MXzander
left a comment
There was a problem hiding this comment.
content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/about-writing-and-formatting-on-github.md
|
|
||
| Described in [Jetton Offchain Payloads](https://github.com/ton-blockchain/TEPs/blob/master/text/0000-jetton-offchain-payloads.md) TEP. | ||
|
|
||
| ### GetMethods |
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
There was a problem hiding this comment.
0x460a252b4feefa821d3351731220627d7b7d1f3d
|
این من نیستم که برداشت میکنه
در تاریخ شنبه ۱۲ آوریل ۲۰۲۵، ۱۸:۰۱ Abreham Bahru ***@***.***>
نوشت:
… ***@***.**** commented on this pull request.
------------------------------
In text/0000-compressed-jetton-standard.md
<#177 (comment)>:
> +In addition to standard fields (like balance, owner, etc), this standard suggest to store `merkle_hash` 256-bit integer in JettonMaster and JettonWallet contracts. Additionally all JettonWallet contracts stores flag `already_claimed` whether airdrop was claimed or not.
+
+### Handlers
+
+Standard TEP-74 Jetton implements the `transfer` handler with the following scheme:
+
+```
+transfer#0f8a7ea5 query_id:uint64 amount:(VarUInteger 16) destination:MsgAddress
+ response_destination:MsgAddress custom_payload:(Maybe ^Cell)
+ forward_ton_amount:(VarUInteger 16) forward_payload:(Either Cell ^Cell)
+ = InternalMsgBody;
+```
+
+This standard propose to use `custom_payload` to store there _claim airdrop_ command with the following scheme:
+```
+merkle_airdrop_claim proof:^Cell = CustomPayload;
Fine
—
Reply to this email directly, view it on GitHub
<#177 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BQAFJOZH3ACRZ2YYGLRKARL2ZEPV3AVCNFSM6AAAAABLJELB2WVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDONRSGE3TGNJXHA>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Cs9Lx1gY5c
left a comment
There was a problem hiding this comment.
UQCik2k4A_gjTGXmWCoUP2ram33asHx2JxFhOeNYd4ub4tbh
No description provided.