Skip to content
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

Contract verification on Optimism Goerli displays wrong URL #3288

Closed
WarTech9 opened this issue Oct 21, 2022 · 3 comments · Fixed by #3299
Closed

Contract verification on Optimism Goerli displays wrong URL #3288

WarTech9 opened this issue Oct 21, 2022 · 3 comments · Fixed by #3299
Assignees

Comments

@WarTech9
Copy link

After verifying a contract with hardhat-etherscan plugin, a message is displayed showing the successful status and the URL to the newly verified contract on Etherscan:

Successfully verified contract ${contractName} on Etherscan.
https://goerli-optimistic.etherscan.io/address/${contractAddress}#code

The URL displayed points to https://goerli-optimistic.etherscan.io

Opening this URL does not work because the block explorer URL for goerli is https://goerli-optimism.etherscan.io/ (optimism not optimistic).

While Etherscan seems to have a redirect from optimistic to optimism, this does not include the path after redirecting, thus, opening the link displayed does not take you to the page for your contract.

@github-actions
Copy link
Contributor

This issue is also being tracked on Linear.

We use Linear to manage our development process, but we keep the conversations on Github.

LINEAR-ID: f7f6a3f3-de93-40e8-bab0-3fa46f71e574

@fvictorio
Copy link
Member

Great catch, thanks a lot for reporting this @WarTech9!

@fvictorio
Copy link
Member

Fixed in @nomiclabs/hardhat-etherscan@3.1.2.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jan 26, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants