ERC 20

The ERC20 ISSUE plugin simplifies the issuance process by allowing users to issue ERC20 tokens with different features through simple configuration.

Issuing Token

When issuing Token, you can configure different issuance modes according to the different functions required for the Token, and the configurable parameters are as follows

Governance Configuration: Governance Coin (Manual Agent), Governance Coin (Default Agent), Snapshot Coin, Non-Snapshot Coin

Precision settings: default precision: 18 bits; custom precision: 1-18 bits, some (such as USDT) for 6 bits, the precision of the tokens affects the smallest unit of the tokens can be split, the general ERC20 tokens and the ETH precision are consistent with the 18-bit, you can choose the default precision (18)

Minting configuration: can be divided into minting and non-minting, (only minting: tokens are all generated by minting, can modify the minting right owner, applicable to the scenario where all tokens are generated by minting, for example, all the tokens are obtained by mining and cut without upper limit)

Pre-mining configuration: you can pre-mining, pre-mining will default pre-mining to the configurator's account (only pre-mining: tokens can not be minted, the creation of pre-mining to its address, applicable to only the initial allocation, not the incremental distribution of the scenario, the pre-mining of a unified address through the transfer of multi-signature contracts, such as the allocation)

Issue cap: you can configure whether the tokens have a minting cap, and whether to support incremental issuance, according to the specific tokens for business purposes (with cap: represents the upper limit of the total number of tokens that can be produced, and the upper limit in the pre-mining mode only is the same as the number of pre-mined by default and is not configurable). No upper limit: represents no upper limit of tokens, only in pre-mining mode, the upper limit is the same as the number of pre-mined tokens, and cannot be configured.)

Destruction configuration: configure whether the tokens support destruction (the default address is the destruction address, the tokens can not be transferred to this address by default, if the destruction is turned on, it means that the tokens can be transferred to this address on behalf of the destruction)

Pause configuration: configure whether the token contract can be paused, pause the token contract will be unavailable (support pause can manage to deactivate the Token transfer function, do not support can not deactivate the transfer)

Blacklist configuration: blacklisted users will not be able to transfer/destroy tokens

Admin Management

1) Minting tokens

Users who have the right to mint tokens can mint tokens in Admin: enter the number of tokens to be minted and the minting target address

2）Authority Configuration

You can configure the Admin, Mint, Destroy and Suspend rights of tokens to the target user.

Admin: Administrator, able to assign token management rights (add or revoke other rights)

Miner: minting rights, can mint tokens

Burner: Destruction rights, can destroy mintable tokens

Puuser: Suspend rights, can suspend the token contract, make the token contract temporarily invalid, minting, transfer, etc. are not available

(3) If the issuance of support for modifying the maximum number of tokens, you can also modify the maximum number of tokens here