docs: fix contract verification #572
Open
Conversation
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
This PR updates the “Verifying Your Contract” section in the Foundry deployment guide.
Previously, the documentation referenced Etherscan verification using --etherscan-api-key while targeting the Ink Sepolia network, which uses Blockscout instead.
This caused confusion and verification failures when developers attempted to verify contracts on Ink.
Changes
Replaced all mentions of Etherscan with Blockscout.
Updated the example forge verify-contract command to use the proper Blockscout verifier flags:
forge 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
Clarified that the Ink Sepolia network is verified through Blockscout, not Etherscan.
Aligned environment variable names (INKSEPOLIA_RPC_URL instead of RPC_URL) for consistency with Foundry profiles.
Why
Etherscan and Blockscout use different APIs and are not interchangeable.
Ink’s Sepolia network is powered by Blockscout, so verification must target its API endpoint (https://explorer-sepolia.inkonchain.com/api).
Without this fix, forge verify-contract fails with an “unsupported chain” error.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This PR updates the “Verifying Your Contract” section in the Foundry deployment guide. Previously, the documentation referenced Etherscan verification using --etherscan-api-key while targeting the Ink Sepolia network, which uses Blockscout instead.
This caused confusion and verification failures when developers attempted to verify contracts on Ink.
Changes:
Replaced all mentions of Etherscan with Blockscout.
Updated the example forge verify-contract command to use the proper Blockscout verifier flags: forge 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
Clarified that the Ink Sepolia network is verified through Blockscout, not Etherscan.
Aligned environment variable names (INKSEPOLIA_RPC_URL instead of RPC_URL) for consistency with Foundry profiles.
Why:
Etherscan and Blockscout use different APIs and are not interchangeable. Ink’s Sepolia network is powered by Blockscout, so verification must target its API endpoint (https://explorer-sepolia.inkonchain.com/api). Without this fix, forge verify-contract fails with an “unsupported chain” error.