Comment on page
Integrating ANT
The current version of ANT, ANTv2, is a lightweight, close-to-vanilla ERC-20 token. It is modelled after Uniswap's liquidity provider (LP) tokens.
Right off the bat, if your application handles vanilla ERC-20s (or the aforementioned Uniswap LP tokens) without requiring any other functionality, you should be safe to assume ANT can be integrated into your application.
Contracts integrating ANT cannot assume ANT will have a fixed total supply. This value can change through the
mint() and burn() functionality.Outside of the above note, and unless you want to leverage its extended functionality, you should be safe to assume that ANT is a completely vanilla ERC-20 implementation.
Allows for a third party to submit an approval on behalf of a signer. Commonly used in account delegation schemes with smart contracts pulling tokens from users (with
transferFrom()).Allows for a third party to submit a transfer on behalf of a signer.
Note that ANTv2 does not protect against any frontrunning on the signature provided to
transferWithAuthorization(). This method should only be used if the receiving contract can safely receive tokens through a vanilla transfer() (rather than a transferFrom()).Convenience getter for obtaining the current chain ID known by the token contract.
Convenience getter for obtaining the current ERC-712 domain separator used by the token contract to verify signatures. Useful when constructing and verifying signatures for
permit() and transferWithAuthorization().Allows any holder to burn their tokens to reduce the token's total supply.
Allows the designated
minter to mint new tokens to a specific account.Currently set to the Community Multisig.
Allows the designated
minter to transfer the minting role to another account.Last modified 6mo ago