NFT transfer is an operation specified in TEP 0062. Its implementation must comply with this standard, and NFT item contracts must support the logic described there. The NFT transfer message is also specified and must comply with the corresponding TL-B scheme. This scheme involves, among other things,Documentation Index
Fetch the complete documentation index at: https://companyname-a7d5b98e-pr-1003-gas-tolk.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
forward_amount: the amount of nanotons to be sent to the destination address;forward_payload: optional custom data that should be sent to the destination address.
forward_payload field there are specific requirements:
- In the case of a simple comment,
forward_payloadmust starts with0x00000000and the comment must be contained in the remainder of theforward_payload. In turn, 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 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. - 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.
- begins with the byte
- If
forward_payloadcontains a binary message for interacting with the destination smart contract, then there are no prefixes.
<NFT_ITEM_ADDR>— the address of the NFT item to be transferred.<RECEIVER_ADDR>— the address of the recipient.