openzeppelin-contracts/contracts/token/ERC721

---

sections:

• title: Core contracts:
  • IERC721
  • ERC721
  • IERC721Metadata
  • ERC721Metadata
  • ERC721Enumerable
  • IERC721Enumerable
  • IERC721Full
  • ERC721Full
  • IERC721Receiver
• title: Extensions contracts:
  • ERC721Mintable
  • ERC721MetadataMintable
  • ERC721Burnable
  • ERC721Pausable
• title: Convenience contracts:
  • ERC721Holder ---

This set of interfaces, contracts, and utilities are all related to the ERC721 Non-Fungible Token Standard.

For a walkthrough on how to create an ERC721 token read our ERC721 guide.

The EIP consists of three interfaces, found here as IERC721, IERC721Metadata, and IERC721Enumerable. Only the first one is required in a contract to be ERC721 compliant.

Each interface is implemented separately in ERC721, ERC721Metadata, and ERC721Enumerable. You can choose the subset of functionality you would like to support in your token by combining the desired subset through inheritance.

The fully featured token implementing all three interfaces is prepackaged as ERC721Full.

Additionally, IERC721Receiver can be used to prevent tokens from becoming forever locked in contracts. Imagine sending an in-game item to an exchange address that can't send it back!. When using safeTransferFrom(), the token contract checks to see that the receiver is an IERC721Receiver, which implies that it knows how to handle ERC721 tokens. If you're writing a contract that needs to receive ERC721 tokens, you'll want to include this interface.

Finally, some custom extensions are also included:

• ERC721Mintable — like the ERC20 version, this allows certain addresses to mint new tokens
• ERC721Pausable — like the ERC20 version, this allows addresses to freeze transfers of tokens

This page is incomplete. We're working to improve it for the next release. Stay tuned!