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.
 
 
 
 
 
openzeppelin-contracts/contracts/token/ERC20
Francisco Giordano e41daba7b4 merge api docs changes 6 years ago
..
ERC20.sol merge api docs changes 6 years ago
ERC20Burnable.sol merge api docs changes 6 years ago
ERC20Capped.sol merge api docs changes 6 years ago
ERC20Detailed.sol merge api docs changes 6 years ago
ERC20Mintable.sol merge api docs changes 6 years ago
ERC20Pausable.sol Revert Solidity version bump. (#1729) 6 years ago
IERC20.sol merge api docs changes 6 years ago
README.md merge api docs changes 6 years ago
SafeERC20.sol Revert Solidity version bump. (#1729) 6 years ago
TokenTimelock.sol Revert Solidity version bump. (#1729) 6 years ago

README.md

sections
{title Core} {contracts [IERC20 ERC20 ERC20Detailed]}] [{title Extensions} {contracts [ERC20Mintable ERC20Burnable ERC20Pausable ERC20Capped]}] [{title Utilities} {contracts [SafeERC20 TokenTimelock]}

This set of interfaces, contracts, and utilities are all related to the ERC20 Token Standard.

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

There a few core contracts that implement the behavior specified in the EIP: IERC20, ERC20, ERC20Detailed.

Additionally there are multiple extensions, including:

  • designation of addresses that can create token supply (ERC20Mintable), with an optional maximum cap (ERC20Capped),
  • destruction of own tokens (ERC20Burnable),
  • designation of addresses that can pause token operations for all users (ERC20Pausable).

Finally, there are some utilities to interact with ERC20 contracts in various ways.

  • SafeERC20 is a wrapper around the interface that eliminates the need to handle boolean return values.
  • TokenTimelock can hold tokens for a beneficiary until a specified time.

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