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
Add a Verify from Etherscan button on the Smart Contract Verification page, that checks if the contract is already verified at zksync.network and uses that public information to also verify the contract within the Block Explorer.
This button should only be displayed as an option if there's a corresponding Etherscan block explorer for the chain (e.g. Mainnet & Sepolia but not partner ZK chains)
🤔 Rationale
Sometimes there are smart contracts that are not verified on Block Explorer, but are verified on ZKsync's Etherscan explorer. It would be really great if there was an easy/quick option on the Smart Contract Verification page that would attempt to verify the contract based on the information from zksync.network
🌟 Feature Request
📝 Description
Add a
Verify from Etherscan
button on theSmart Contract Verification
page, that checks if the contract is already verified atzksync.network
and uses that public information to also verify the contract within the Block Explorer.This button should only be displayed as an option if there's a corresponding Etherscan block explorer for the chain (e.g. Mainnet & Sepolia but not partner ZK chains)
🤔 Rationale
Sometimes there are smart contracts that are not verified on Block Explorer, but are verified on ZKsync's Etherscan explorer. It would be really great if there was an easy/quick option on the
Smart Contract Verification
page that would attempt to verify the contract based on the information fromzksync.network
📋 Additional Context
Example contract that's verified on Etherscan's Explorer: https://era.zksync.network/address/0xE629B208046F7A33dE3A43931c9FE505A7Ac3d36#code
But unverified on our Block Explorer: https://explorer.zksync.io/contracts/verify?address=0xE629B208046F7A33dE3A43931c9FE505A7Ac3d36
The text was updated successfully, but these errors were encountered: