Ensure ERC20 contracts can be verified on frontends like Etherscan so tokens have legitimacy #239
Labels
needs investigation
Issues that need some research before deciding approach or feasibility
solidity
Issues related to the solidity contracts
On Etherscan, tokens have an associated reputation - the default is Unknown, but the desirable reputation for a project is OK, or at least neutral. In order to have an OK and neutral reputation, a contract source code has to be verified and you have to verify that you are the contract owner, as well as other social accreditations, which are outside of scope here. This has been a problem for cheqd using gravity bridge as they have not been able to verify ownership of their token.
To ensure that IBC bridged assets look legitimate, we should ensure that we are able to verify the ERC20s deployed on Ethereum. It seems that the verification can also be done on the origin rather than destination. There is more information here.
Before launch we should ensure that we have a means to verify ERC20 deployments and the IBC core solidity contracts.
The text was updated successfully, but these errors were encountered: