ERC 721
| This document is better viewed at https://docs.openzeppelin.com/contracts/api/token/erc721 |
This set of interfaces, contracts, and utilities are all related to the ERC721 Non-Fungible Token Standard.
| For a walk through 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. However, all three are implemented in ERC721.
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.
Additionally there are multiple custom extensions, including:
-
designation of addresses that can pause token transfers for all users (
ERC721Pausable). -
destruction of own tokens (
ERC721Burnable).
This core set of contracts is designed to be unopinionated, allowing developers to access the internal functions in ERC721 (such as _mint) and expose them as external functions in the way they prefer. On the other hand, ERC721 Presets (such as ERC721PresetMinterPauserAutoId) are designed using opinionated patterns to provide developers with ready to use, deployable contracts.
|
Core
IERC721
Required interface of an ERC721 compliant contract.
balanceOf(address owner) → uint256 balance external
Returns the number of tokens in owner's account.
ownerOf(uint256 tokenId) → address owner external
Returns the owner of the tokenId token.
Requirements:
-
tokenIdmust exist.
safeTransferFrom(address from, address to, uint256 tokenId) external
Safely transfers tokenId token from from to to, checking first that contract recipients
are aware of the ERC721 protocol to prevent tokens from being forever locked.
Requirements:
-
fromcannot be the zero address. -
tocannot be the zero address. -
tokenIdtoken must exist and be owned byfrom. -
If the caller is not
from, it must be have been allowed to move this token by eitherapproveorsetApprovalForAll. -
If
torefers to a smart contract, it must implementIERC721Receiver.onERC721Received, which is called upon a safe transfer.
Emits a Transfer event.
transferFrom(address from, address to, uint256 tokenId) external
Transfers tokenId token from from to to.
Usage of this method is discouraged, use safeTransferFrom whenever possible.
|
Requirements:
-
fromcannot be the zero address. -
tocannot be the zero address. -
tokenIdtoken must be owned byfrom. -
If the caller is not
from, it must be approved to move this token by eitherapproveorsetApprovalForAll.
Emits a Transfer event.
approve(address to, uint256 tokenId) external
Gives permission to to to transfer tokenId token to another account.
The approval is cleared when the token is transferred.
Only a single account can be approved at a time, so approving the zero address clears previous approvals.
Requirements:
-
The caller must own the token or be an approved operator.
-
tokenIdmust exist.
Emits an Approval event.
getApproved(uint256 tokenId) → address operator external
Returns the account approved for tokenId token.
Requirements:
-
tokenIdmust exist.
setApprovalForAll(address operator, bool _approved) external
Approve or remove operator as an operator for the caller.
Operators can call transferFrom or safeTransferFrom for any token owned by the caller.
Requirements:
-
The
operatorcannot be the caller.
Emits an ApprovalForAll event.
isApprovedForAll(address owner, address operator) → bool external
Returns if the operator is allowed to manage all of the assets of owner.
safeTransferFrom(address from, address to, uint256 tokenId, bytes data) external
Safely transfers tokenId token from from to to.
Requirements:
-
fromcannot be the zero address. -
tocannot be the zero address. -
tokenIdtoken must exist and be owned byfrom. -
If the caller is not
from, it must be approved to move this token by eitherapproveorsetApprovalForAll. -
If
torefers to a smart contract, it must implementIERC721Receiver.onERC721Received, which is called upon a safe transfer.
Emits a Transfer event.
Transfer(address from, address to, uint256 tokenId) event
Emitted when tokenId token is transferred from from to to.
IERC721Enumerable
tokenOfOwnerByIndex(address owner, uint256 index) → uint256 tokenId external
Returns a token ID owned by owner at a given index of its token list.
Use along with balanceOf to enumerate all of owner's tokens.
tokenByIndex(uint256 index) → uint256 external
Returns a token ID at a given index of all the tokens stored by the contract.
Use along with totalSupply to enumerate all tokens.
ERC721
constructor(string name_, string symbol_) public
Initializes the contract by setting a name and a symbol to the token collection.
balanceOf(address owner) → uint256 public
See IERC721.balanceOf.
ownerOf(uint256 tokenId) → address public
See IERC721.ownerOf.
name() → string public
See IERC721Metadata.name.
baseURI() → string public
Returns the base URI set via _setBaseURI. This will be
automatically added as a prefix in tokenURI to each token’s URI, or
to the token ID if no specific URI is set for that token ID.
approve(address to, uint256 tokenId) public
See IERC721.approve.
getApproved(uint256 tokenId) → address public
See IERC721.getApproved.
transferFrom(address from, address to, uint256 tokenId) public
See IERC721.transferFrom.
_safeTransfer(address from, address to, uint256 tokenId, bytes _data) internal
Safely transfers tokenId token from from to to, checking first that contract recipients
are aware of the ERC721 protocol to prevent tokens from being forever locked.
_data is additional data, it has no specified format and it is sent in call to to.
This internal function is equivalent to safeTransferFrom, and can be used to e.g.
implement alternative mechanisms to perform token transfer, such as signature-based.
Requirements:
-
fromcannot be the zero address. -
tocannot be the zero address. -
tokenIdtoken must exist and be owned byfrom. -
If
torefers to a smart contract, it must implementIERC721Receiver.onERC721Received, which is called upon a safe transfer.
Emits a Transfer event.
_exists(uint256 tokenId) → bool internal
Returns whether tokenId exists.
Tokens can be managed by their owner or approved accounts via approve or setApprovalForAll.
Tokens start existing when they are minted (_mint),
and stop existing when they are burned (_burn).
_isApprovedOrOwner(address spender, uint256 tokenId) → bool internal
Returns whether spender is allowed to manage tokenId.
Requirements:
-
tokenIdmust exist.
_safeMint(address to, uint256 tokenId) internal
Safely mints tokenId and transfers it to to.
Requirements:
d*
- tokenId must not exist.
- If to refers to a smart contract, it must implement IERC721Receiver.onERC721Received, which is called upon a safe transfer.
Emits a Transfer event.
_safeMint(address to, uint256 tokenId, bytes _data) internal
Same as _safeMint, with an additional data parameter which is
forwarded in IERC721Receiver.onERC721Received to contract recipients.
_mint(address to, uint256 tokenId) internal
Mints tokenId and transfers it to to.
Usage of this method is discouraged, use _safeMint whenever possible
|
Requirements:
-
tokenIdmust not exist. -
tocannot be the zero address.
Emits a Transfer event.
_burn(uint256 tokenId) internal
Destroys tokenId.
The approval is cleared when the token is burned.
Requirements:
-
tokenIdmust exist.
Emits a Transfer event.
_transfer(address from, address to, uint256 tokenId) internal
Transfers tokenId from from to to.
As opposed to transferFrom, this imposes no restrictions on msg.sender.
Requirements:
-
tocannot be the zero address. -
tokenIdtoken must be owned byfrom.
Emits a Transfer event.
_setTokenURI(uint256 tokenId, string _tokenURI) internal
Sets _tokenURI as the tokenURI of tokenId.
Requirements:
-
tokenIdmust exist.
_beforeTokenTransfer(address from, address to, uint256 tokenId) internal
Hook that is called before any token transfer. This includes minting and burning.
Calling conditions:
-
When
fromandtoare both non-zero,from'stokenIdwill be transferred toto. -
When
fromis zero,tokenIdwill be minted forto. -
When
tois zero,from'stokenIdwill be burned. -
fromcannot be the zero address. -
tocannot be the zero address.
To learn more about hooks, head to Using Hooks.
IERC721Receiver
Interface for any contract that wants to support safeTransfers from ERC721 asset contracts.
onERC721Received(address operator, address from, uint256 tokenId, bytes data) → bytes4 external
Whenever an IERC721 tokenId token is transferred to this contract via IERC721.safeTransferFrom
by operator from from, this function is called.
It must return its Solidity selector to confirm the token transfer. If any other value is returned or the interface is not implemented by the recipient, the transfer will be reverted.
The selector can be obtained in Solidity with IERC721.onERC721Received.selector.
Extensions
ERC721Pausable
ERC721 token with pausable token transfers, minting and burning.
Useful for scenarios such as preventing trades until the end of an evaluation period, or having an emergency switch for freezing all token transfers in the event of a large bug.
ERC721Burnable
ERC721 Token that can be irreversibly burned (destroyed).
burn(uint256 tokenId) public
Burns tokenId. See ERC721._burn.
Requirements:
-
The caller must own
tokenIdor be an approved operator.
Convenience
ERC721Holder
Implementation of the IERC721Receiver interface.
Accepts all token transfers.
Make sure the contract is able to use its token with IERC721.safeTransferFrom, IERC721.approve or IERC721.setApprovalForAll.