Replies: 2 comments
Etherscan already has native support for diamondsCheckout the Li.Fi. diamond on Etherscan: https://etherscan.io/address/0x1231DEB6f5749EF6cE6943a275A1D3E7486F4EaE#multipleProxyContract |
0 replies
|
Promote the Interim Solution as a Best Practice: While we agree this pattern should not be mandated, we believe it is highly beneficial to officially document, promote, and support this workaround as a recommended interim best practice. This provides immediate utility and a better user experience for projects deploying diamonds, without locking us into this solution permanently. The provided example is an excellent starting point for this documentation. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment

Uh oh!
There was an error while loading. Please reload this page.
Problem, Etherscan is no "Diamond Aware". Some ERC standards for proxies are supported by Etherscan, but not Diamonds. In the meantime, there is a design pattern that "shoehorns" Diamond support into Etherscan with a mock contracts to get an ABI for all the Facets to populate the interaction UI on Etherscan.
There's and example here.
I don't think this pattern should be mandated. But does this project want to pursue promoting this "hack" in the meantime. Ideally, with the aim of pushing Etherscan to natively supporting Diamonds. And possibly, committing resources to developing a patch and issuing a PR to Etherscan to get Diamond support.
All reactions