From dafd73e4985459bdd666e9de81a698bb8e383ba6 Mon Sep 17 00:00:00 2001
From: Penzlik <schoolkam@gmail.com>
Date: Tue, 28 Jul 2026 10:45:18 +0300
Subject: [PATCH] fix(docs): use Blockscout verifier flags in Foundry
 verification example

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 #609
---
 .../build/tutorials/deploying-a-smart-contract/foundry.mdx  | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/src/pages/build/tutorials/deploying-a-smart-contract/foundry.mdx b/src/pages/build/tutorials/deploying-a-smart-contract/foundry.mdx
index da4ea397..223974ef 100644
--- a/src/pages/build/tutorials/deploying-a-smart-contract/foundry.mdx
+++ b/src/pages/build/tutorials/deploying-a-smart-contract/foundry.mdx
@@ -156,12 +156,14 @@ forge script script/Deploy.s.sol:DeployScript --rpc-url $RPC_URL --broadcast --v
 
 ## Verifying Your Contract
 
-If you want to verify your contract on Etherscan:
+If you want to verify your contract on Blockscout:
 
 ```bash
 forge verify-contract <DEPLOYED_CONTRACT_ADDRESS> src/InkContract.sol:InkContract \
     --chain-id 763373 \
-    --etherscan-api-key $BLOCKSCOUT_API_KEY
+    --verifier blockscout \
+    --verifier-url https://explorer-sepolia.inkonchain.com/api \
+    --verifier-api-key $BLOCKSCOUT_API_KEY
 ```
 
 ## Additional Configuration