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.
Funds at riskBeware that API keys and mnemonic must not be committed or shared publicly.A better approach is to use a
.env file that is excluded from repository with .gitignore. For GitHub CI purposes, consult their documentation.<NFT_ITEM_ADDR>— the address of the NFT item to be transferred.<RECEIVER_ADDR>— the address of the recipient.