Skip to content

fix(docs): use Blockscout verifier flags in Foundry verification example - #633

Open
schoolkamsergj wants to merge 1 commit into
inkonchain:mainfrom
schoolkamsergj:fix/foundry-blockscout-verifier
Open

fix(docs): use Blockscout verifier flags in Foundry verification example#633
schoolkamsergj wants to merge 1 commit into
inkonchain:mainfrom
schoolkamsergj:fix/foundry-blockscout-verifier

Conversation

@schoolkamsergj

Copy link
Copy Markdown

Summary

The Foundry deployment guide uses --etherscan-api-key in the contract verification example, but Ink Sepolia verifies through Blockscout, not Etherscan. As reported in #609, this makes forge verify-contract fail with an "unsupported chain" error.

Change

Before:

forge verify-contract <DEPLOYED_CONTRACT_ADDRESS> src/InkContract.sol:InkContract
--chain-id 763373
--etherscan-api-key $BLOCKSCOUT_API_KEY

After:
orge verify-contract <DEPLOYED_CONTRACT_ADDRESS> src/InkContract.sol:InkContract
--chain-id 763373
--verifier blockscout
--verifier-url https://explorer-sepolia.inkonchain.com/api
--verifier-api-key $BLOCKSCOUT_API_KEY

Also updates the section wording from "on Etherscan" to "on Blockscout" for consistency.

Notes

Minimal diff: 2 lines removed, 4 added, no other content touched. Commit is GPG-signed.

Closes #609

Ink Sepolia contract verification goes through Blockscout, not Etherscan. The --etherscan-api-key flag causes forge verify-contract to fail with an unsupported chain error.

Replaces it with --verifier blockscout, --verifier-url and --verifier-api-key, and updates the section wording accordingly.

Closes inkonchain#609
@schoolkamsergj
schoolkamsergj requested a review from a team as a code owner July 28, 2026 08:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

1 participant