Contracts in this category should be considered unstable. They are as thoroughly reviewed as everything else in OpenZeppelin Contracts, but we have doubts about their API so we don’t commit to backwards compatibility. This means these contracts can receive breaking changes in a minor version, so you should pay special attention to the changelog when upgrading. For anything that is outside of this category you can read more about API Stability.
|This page is incomplete. We’re working to improve it for the next release. Stay tuned!|
This contract can be used to migrate an ERC20 token from one
contract to another, where each token holder has to opt-in to the migration.
To opt-in, users must approve for this contract the number of tokens they
want to migrate. Once the allowance is set up, anyone can trigger the
migration to the new token contract. In this way, token holders "turn in"
their old balance and will be minted an equal amount in the new token.
The new token contract must be mintable. For the precise interface refer to
ERC20Mintable, but the only functions that are needed are
ERC20Mintable.mint. The migrator will check
that it is a minter for the token.
The balance from the legacy token will be transferred to the migrator, as it
is migrated, and remain there forever.
Although this contract can be used in many different scenarios, the main
motivation was to provide a way to migrate ERC20 tokens into an upgradeable
version of it using ZeppelinOS. To read more about how this can be done
using this implementation, please follow the official documentation site of
Example of usage:
const migrator = await ERC20Migrator.new(legacyToken.address); await newToken.addMinter(migrator.address); await migrator.beginMigration(newToken.address);
Begins the migration by setting which is the new token that will be minted. This contract must be a minter for the new token.
Transfers part of an account’s balance in the old token to this contract, and mints the same amount of new tokens for that account.
This contract extends an ERC20 token with a snapshot mechanism. When a snapshot is created, the balances and total supply at the time are recorded for later access.
This can be used to safely create mechanisms based on token balances such as trustless dividends or weighted voting. In naive implementations it’s possible to perform a "double spend" attack by reusing the same balance from different accounts. By using snapshots to calculate dividends or voting power, those attacks no longer apply. It can also be used to create an efficient ERC20 forking mechanism.
Snapshots are created by the internal
Snapshot function, which will emit the
Snapshot event and return a
snapshot id. To get the total supply at the time of a snapshot, call the function
totalSupplyAt with the snapshot
id. To get the balance of an account at the time of a snapshot, call the
balanceOfAt function with the snapshot id
and the account address.
Snapshots are efficient. Snapshot creation is O(1). Retrieval of balances or total supply from a snapshot is O(log n) in the number of snapshots that have been created, although n for a specific account will generally be much smaller since identical balances in subsequent snapshots are stored as a single entry.
There is a constant overhead for normal ERC20 transfers due to the additional snapshot bookkeeping. This overhead is only significant for the first transfer that immediately follows a snapshot for a particular account. Subsequent transfers will have normal cost until the next snapshot, and so on.
Creates a new snapshot and returns its snapshot id.
Snapshot event that contains the same id.
A public function could potentially be used by attackers in two ways.
First, it can be used to increase the cost of retrieval of values from snapshots, although it will grow logarithmically thus rendering this attack ineffective in the long term. Second, it can be used to target specific accounts and increase the cost of ERC20 transfers for them, in the ways specified in the Gas Costs section above.
We haven’t measured the actual numbers; if this is something you’re interested in please reach out to us.
Retrieves the balance of
account at the time
snapshotId was created.
Retrieves the total supply at the time
snapshotId was created.
Snapshot when a snapshot identified by
id is created.
A token holder contract that can release its token balance gradually like a typical vesting scheme, with a cliff and vesting period. Optionally revocable by the owner.
constructor(address beneficiary, uint256 start, uint256 cliffDuration, uint256 duration, bool revocable) public
Creates a vesting contract that vests its balance of any ERC20 token to the beneficiary, gradually in a linear fashion until start + duration. By then all of the balance will have vested.
Provides counters that can only be incremented or decremented by one. This can be used e.g. to track the number of elements in a mapping, issuing ERC721 ids, or counting request ids.
using Counters for Counters.Counter;
Since it is not possible to overflow a 256 bit integer with increments of one,
increment can skip the
overflow check, thereby saving gas. This does assume however correct usage, in that the underlying
_value is never
Signed math operations with safety checks that revert on error.
Integer division of two signed integers truncating the quotient, reverts on division by zero.