Examples: query, "exact match", wildcard*, wild?ard, wild*rd
Fuzzy search: cake~ (finds cakes, bake)
Term boost: "red velvet"^4, chocolate^2
Field grouping: tags:(+work -"fun-stuff")
Escape special characters +-&|!(){}[]^"~*?:\ - e.g. \+ \* \!
Range search: properties.timestamp:[1587729413488 TO *] (inclusive), properties.title:{A TO Z}(excluding A and Z)
Combinations: chocolate AND vanilla, chocolate OR vanilla, (chocolate OR vanilla) NOT "vanilla pudding"
Field search: properties.title:"The Title" AND text
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

Posted one year ago
Votes Newest


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

Posted one year ago
1 Answer
one year ago
one year ago