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 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.

Originally posted by @HarleyQeen in https://github.com/inkonchain/docs/pull/572

Locate the Foundry deployment guide and its “Verifying Your Contract” section. Check all Etherscan references and the example forge verify-contract command, then update them for Blockscout, including the Ink Sepolia verifier URL, API key, and INKSEPOLIA_RPC_URL naming. Done means the section consistently describes Blockscout verification and the command targets chain ID 763373.