fix(docs): replace --etherscan-api-key with Blockscout verifier flags in Foundry guide#614
Open
schoolkamsergj wants to merge 1 commit into
Open
Conversation
… in Foundry guide
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fixes the incorrect contract verification command in the Foundry deployment guide raised in #609.
The
foundry.mdxguide used--etherscan-api-keyflag when targeting Ink Sepolia network, which uses Blockscout — not Etherscan. This causedforge verify-contractto fail with an "unsupported chain" error.Change
Replaced the incorrect Etherscan flag with the proper Blockscout verifier flags.
Before:
After:
Also updated the section heading from "on Etherscan" to "on Blockscout" for consistency.
Why
https://explorer-sepolia.inkonchain.com/apiforge verify-contractfails for all Ink Sepolia deploymentsCloses #609