README.adoc 2.4 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667
  1. = ERC 721
  2. [.readme-notice]
  3. NOTE: This document is better viewed at https://docs.openzeppelin.com/contracts/api/token/erc721
  4. This set of interfaces, contracts, and utilities are all related to the https://eips.ethereum.org/EIPS/eip-721[ERC721 Non-Fungible Token Standard].
  5. TIP: For a walk through on how to create an ERC721 token read our xref:ROOT:erc721.adoc[ERC721 guide].
  6. The EIP specifies four interfaces:
  7. * {IERC721}: Core functionality required in all compliant implementation.
  8. * {IERC721Metadata}: Optional extension that adds name, symbol, and token URI, almost always included.
  9. * {IERC721Enumerable}: Optional extension that allows enumerating the tokens on chain, often not included since it requires large gas overhead.
  10. * {IERC721Receiver}: An interface that must be implemented by contracts if they want to accept tokens through `safeTransferFrom`.
  11. OpenZeppelin Contracts provides implementations of all four interfaces:
  12. * {ERC721}: The core and metadata extensions, with a base URI mechanism.
  13. * {ERC721Enumerable}: The enumerable extension.
  14. * {ERC721Holder}: A bare bones implementation of the receiver interface.
  15. Additionally there are a few of other extensions:
  16. * {ERC721URIStorage}: A more flexible but more expensive way of storing metadata.
  17. * {ERC721Votes}: Support for voting and vote delegation.
  18. * {ERC721Royalty}: A way to signal royalty information following ERC2981.
  19. * {ERC721Pausable}: A primitive to pause contract operation.
  20. * {ERC721Burnable}: A way for token holders to burn their own tokens.
  21. NOTE: This core set of contracts is designed to be unopinionated, allowing developers to access the internal functions in ERC721 (such as <<ERC721-_mint-address-uint256-,`_mint`>>) and expose them as external functions in the way they prefer. On the other hand, xref:ROOT:erc721.adoc#Presets[ERC721 Presets] (such as {ERC721PresetMinterPauserAutoId}) are designed using opinionated patterns to provide developers with ready to use, deployable contracts.
  22. == Core
  23. {{IERC721}}
  24. {{IERC721Metadata}}
  25. {{IERC721Enumerable}}
  26. {{ERC721}}
  27. {{ERC721Enumerable}}
  28. {{IERC721Receiver}}
  29. == Extensions
  30. {{ERC721Pausable}}
  31. {{ERC721Burnable}}
  32. {{ERC721URIStorage}}
  33. {{ERC721Votes}}
  34. {{ERC721Royalty}}
  35. == Presets
  36. These contracts are preconfigured combinations of the above features. They can be used through inheritance or as models to copy and paste their source code.
  37. {{ERC721PresetMinterPauserAutoId}}
  38. == Utilities
  39. {{ERC721Holder}}