-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Explorer doesn't display ERC20 token name, symbol and token holders #145
Comments
Same issue for ZUSD, an upgradeable RBTC-backed stablecoin issued by the Zero protocol: Proxy: https://explorer.rsk.co/address/0xdb107fa69e33f05180a4c2ce9c2e7cb481645c2d Here is a sample ZUSD holder: https://explorer.rsk.co/address/0xd28aaacaa524f50da5c6025ca5a5e1a8cbf84647 ZUSD does not show up in the "Tokens" tab, or the "Token Transfers" tab of the user's address. Even if you go directly to a ZUSD transaction, the transfer is not picked up in the transaction's "Token Transfers" tab: https://explorer.rsk.co/tx/0x68ec06544a7e74efd6d44f0d9780635b19ac6d0361a102626627f1b4e4781449?__ctab=Token%20Transfers It is very difficult for users to figure out what is going on with ZUSD transactions using RSK Explorer. |
I've deployed an upgradable ERC20 contract, everything works fine and I interact with it via RPC but the RSK block explorer doesn't display it well - there is no token name or symbol, and the Accounts tab, which should display all token holders, is empty.
The proxy contract implements Open-Zeppelin's
OptimizedTransparentUpgradeableProxy
Contract address: 0xd96AA50B7f306ab20425cD6F213128AdF7eb1f0E
Block Explorer: https://explorer.rsk.co/address/0xd96aa50b7f306ab20425cd6f213128adf7eb1f0e
I see that the block explorer recognizes it's an ERC20, but still no token name, symbol or holders are displayed.
The implementation contract:
Contract address: 0x6542a10E68ceAC1fa0641ec0D799a7492795aaC1
Block Explorer: https://explorer.rsk.co/address/0x6542a10e68ceac1fa0641ec0d799a7492795aac1
Both contracts are verified on the block explorer.
The text was updated successfully, but these errors were encountered: