TEP-62
NFT Item
Transfer message layout
Forward payload formats
To send a simple comment in theforward_payload, the forward_payload must start with 0x00000000 (32-bit unsigned integer equal to zero); the remainder of the forward_payload contains the comment.
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.
Ownership assigned message layout
Excesses message layout
Get static data message layout
Report static data message layout
get_nft_data()
No arguments. Outputs:NFT Collection
get_collection_data()
No arguments. Outputs:get_nft_address_by_index()
Argument:index as int.
Output: address as MsgAddress.
get_nft_content()
Arguments:indexasintindividual_contentasCell
full_content as Cell.
TEP-66
Get royalty params message layout
Report royalty params message layout
royalty_params()
No arguments. Outputs:
Royalty share is
numerator / denominator. For example, if numerator = 11 and denominator = 1000, then royalty share is 11 / 1000 * 100% = 1.1%.