Closed iquidus closed 4 years ago
Candidates:
1: Disable 2: Keep enabled 3: Abstain
Updated OP with total ESCH supply after airdrop #8: 450,454,965.391453439756557953 ESCH
The voting period for UIP7 - Permanently disable Escher minting, has concluded.
Voting contract: 0x293e27B404B0FeD5EE857CF5551cf105f8DD9d7d Start Block : 1215000 End Block : 1245000
Results:
1: Yes (disable) - 92.53% 2: No (keep enabled) - 6.33% 3: Abstain (0.84%)
Simple Summary
With the original 8 planned airdrops drawing to an end, it's time to evaluate how to move forward with the Escher (ESCH) token. Continue as originally planned, or..?
Motivation
Due to the nature of the airdrop schedule, the Escher ERC20 token was deployed with an owner address that has escalated permissions within the contract allowing it to:
The address that currently has this ownership role is: 0xda904bc07fd95e39661941b3f6daded1b8a38c71
This proposal is to continue with the original plan, permanently disable minting. This locks the total supply in at 450,454,965.391453439756557953 ESCH, while also removing any meaniful functionality the ownership role has.
Implementation
If passed (disable), address 0xda904bc07fd95e39661941b3f6daded1b8a38c71 will call the finishMinting function within the Escher ERC20 contract (0xcf3222b7FDa7a7563b9E1E6C966Bead04AC23c36), permanently disabling minting.
If rejected (keep enabled), a second UIP will be submitted to determine how to manage the ownership role/keys.
References
Escher token contract: https://github.com/ubiq/escher-contracts/blob/master/token/ERC20/Escher.sol
About Escher: https://blog.ubiqsmart.com/understanding-the-escher-token-system-80dcae231324