ERC-20 Token
Last updated
Last updated
Token following the or standard.
name()
symbol()
decimals()
totalSupply()
balanceOf(address _owner)
getOwner()
transfer(address _to, uint256 _value)
transferFrom(address _from, address _to, uint256 _value)
approve(address _spender, uint256 _value)
allowance(address _owner, address _spender)
And the usual events.
event Transfer(address indexed _from, address indexed _to, uint256 _value)
event Approval(address indexed _owner, address indexed _spender, uint256 _value)
Typical interaction with the contract will use transfer to move the token as payment. Additionally, a pattern involving approve and transferFrom can be used to allow another address to move tokens from your address to a third party without the need for the middleman to custody the tokens.
It is possible to add functionalities of minting new tokens and burning tokens. Then, there will be a single contract owner address that can mint the tokens. Burning can be done from any wallet address.
To facilitate upgradeability on the immutable blockchain we can follow a standard two-contract delegation pattern: a proxy contract represents the token, while all calls not involving upgrading the contract are delegated to an implementation contract.
The delegation uses delegatecall, which runs the code of the implementation contract in the context of the proxy storage. This way the implementation pointer can be changed to a different implementation contract while still keeping the same data and token contract address, which are really for the proxy contract.
name: Revenue Coin symbol: RVC decimals: 18 (default) premint: 8 888 888 888 (how many tokens to create initially?) minting? burning? meta-transactions? upgradeability proxy? antibot? (i.e. delay: 30s, transaction limit: 1 000 000 tokens)
2 days
In order to allow for gasless transactions it is possible to implement a recently finalized .
It is possible to add an anti-bot feature which makes it impossible for automated programs to front-run transactions made on decentralized exchanges. You can read more about front-running here . Another feature of anti-bot is setting the maximum amount of tokens the wallet can send in one transaction and the delay between sending transactions from one wallet. It is also possible to whitelist addresses (including smart contracts) that will be ignored by anti-bot.
Learn more about our tokenization services at