There is a "standard" for that, and the error code is 0xffff. It's used in the official smart contract as well: https://github.com/ton-blockchain/token-contract/blob/main/nft/nft-collection.fc#L132
Answered
Is there a convention for the "unsupported opcode" error code?
What error code should a smart contract use when dealing with an unsupported opcode? Is it up to the smart contract developer, or there is a conventional one for everyone to use?
This question was imported from Telegram Chat: https://t.me/tondev/114747
11K Views
1
Answer
one year ago
one year ago
Tags