TEP 0074
Transfer message layout
Forward payload formats
If you want to send a simple comment in theforward_payload, then the forward_payload must start with 0x00000000 (32-bit unsigned integer equals to zero) and the comment is contained in the remainder of the forward_payload.
If the comment does not begin with the byte 0xff, the comment is a text one; it can be displayed “as is” to the end user of a wallet (after filtering invalid and control characters and checking that it is a valid UTF-8 string). For instance, users may indicate the purpose (“for coffee”) of a simple transfer from their wallet to the wallet of another user in this text field.
On the other hand, if the comment begins with the byte 0xff, the remainder is a “binary comment”, which should not be displayed to the end user as text (only as a hex dump if necessary). The intended use of “binary comments” is, e.g., to contain a purchase identifier for payments in a store, to be automatically generated and processed by the store’s software.
If the forward_payload contains a binary message for interacting with the destination smart contract (for example, with DEX), then there are no prefixes.
Transfer notification message layout
Excesses message layout
Burn message layout
get_wallet_data()
No arguments. Outputs:get_jetton_data()
No arguments. Outputs:get_wallet_address()
Argument:owner_address as MsgAddress.
Output: jetton_wallet_addressas MsgAddress.