Expand description
The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are to be interpreted as described in RFC 2119.
Every ERC-721 compliant contract must implement the ERC721 and ERC165 interfaces (subject to “caveats” below):
Enums§
Traits§
- ERC721
- @title ERC-721 Non-Fungible Token Standard @dev See https://eips.ethereum.org/EIPS/eip-721 Note: the ERC-165 identifier for this interface is 0x80ac58cd.
- ERC721
Metadata - The metadata extension is OPTIONAL for ERC-721 smart contracts. This allows your smart contract to be interrogated for its name and for details about the assets which your NFTs represent.
- ERC721
Token Receiver - A wallet/broker/auction application MUST implement the wallet interface if it will accept safe transfers.