You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently interacting with an upgradeable contract displays the name of the proxy contract and not the implementation contract. This is confusing, because the proxies usually have vague names that don't mean much to the users. It would be great if the underlying contract name was displayed instead.
An example of an interaction with the ManagedProxy contract that is an upgradeable proxy for the contract named Drips. It would be clearer if the notification said "sent 10 USDC to Drips", it's the name of the protocol that the user is familiar with. This is the contract: https://etherscan.io/address/0xd0Dd053392db676D57317CD4fe96Fc2cCf42D0b4.
I'm wildly speculating, but you probably are using Etherscan to get information about the contracts, and hey have very good proxy detection, do they expose information like the implementation contract in their API?
The text was updated successfully, but these errors were encountered:
@CodeSandwich Hi, thanks for the report. We actually already do what you suggest and try to pick the better name.
HOWEVER, this can happen because sometiimes we pull this data before etherscan is aware of the implementation contract. We try to avoid hitting etherscan again due to its depressing rate limits (even on a paid plan) so this bad name sticks around.
We ticketed work internally to do some work to recrawl for names on proxy contracts. If you see any wonky names in the meantime, feel free to report to [email protected] as these names can be updated internally. I've updated the name for this particular contract and it should propagate in a few hours.
Currently interacting with an upgradeable contract displays the name of the proxy contract and not the implementation contract. This is confusing, because the proxies usually have vague names that don't mean much to the users. It would be great if the underlying contract name was displayed instead.
An example of an interaction with the
ManagedProxy
contract that is an upgradeable proxy for the contract namedDrips
. It would be clearer if the notification said "sent 10 USDC to Drips", it's the name of the protocol that the user is familiar with. This is the contract: https://etherscan.io/address/0xd0Dd053392db676D57317CD4fe96Fc2cCf42D0b4.I'm wildly speculating, but you probably are using Etherscan to get information about the contracts, and hey have very good proxy detection, do they expose information like the implementation contract in their API?
The text was updated successfully, but these errors were encountered: