mirror
/
openzeppelin-contracts
mirror of https://github.com/OpenZeppelin/openzeppelin-contracts
2
1
Fork 1
Code Issues Releases Wiki Activity
mirror of openzeppelin-contracts
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
1648 Commits
56 Branches
139 Tags
72 MiB
 
 
 
 
 
Tag: Branch: Tree: d9d1082247
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'd9d1082247'
${ noResults }
openzeppelin-contracts/contracts/token/ERC721/README.md

1.3 KiB
Raw Blame History

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.

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