diff --git a/foundry.toml b/foundry.toml
index 1911cb1..346a997 100644
--- a/foundry.toml
+++ b/foundry.toml
@@ -125,10 +125,11 @@ ethereum = { key = "${CI_DEPLOY_ETHEREUM_ETHERSCAN_API_KEY}", chain = 1 }
 flare = { key = "${CI_DEPLOY_FLARE_ETHERSCAN_API_KEY}", chain = 14 }
 hyperevm = { key = "${CI_DEPLOY_HYPEREVM_ETHERSCAN_API_KEY}", chain = 999 }
 # Robinhood Chain (4663) is not indexed by Etherscan V2. Its Blockscout speaks
-# the Etherscan API, so the entry points there (the key is ignored). That
-# explorer has rejected non-browser clients, so if `--verify` fails there,
-# verify afterwards through Sourcify: `forge verify-contract --verifier
-# sourcify --chain 4663 ...`.
+# the Etherscan API, so the entry points there (the key is ignored), but sits
+# behind a Cloudflare challenge that fails `--verify`. Repair through Sourcify
+# with this key set and EMPTY — unset, forge will not start; set, it ignores
+# `--verifier sourcify`. Sourcify's onward pushes then fail and do not matter;
+# `GET /v2/contract/4663/<address>` reporting `"match"` is the verification.
 robinhood = { key = "${CI_DEPLOY_ROBINHOOD_ETHERSCAN_API_KEY}", chain = 4663, url = "https://robinhoodchain.blockscout.com/api" }
 bsc = { key = "${CI_DEPLOY_BSC_ETHERSCAN_API_KEY}", chain = 56 }
 polygon = { key = "${CI_DEPLOY_POLYGON_ETHERSCAN_API_KEY}", chain = 137 }