Improve verify process

[andreivladbrg]

In the flow deployment I have passed for certain chains (major ones) the --verify flag.
It didn't work, and it reverted with the error: Too many api calls

instead of running 1 CLI (forge script <options> --verify --etherscan-api <key>) try to run 2:

1. FOUNDRY_PROFILE=optimized forge script <options>
2. FOUNDRY_PROFILE=optimized forge verify-contract <contract> <options>

---

disclaimer: not sure it will be fixed

[smol-ninja]

Doesn't forge script --verify implies forge script and forge verify-contract under the hood? I think some chain explorers have this rate limiting where if you don't wait for 10 seconds or so, they return Too many api calls error. I have seen it as well.

Recently, I have also seen that forge verify-contract command waits for 10-15 seconds before making another request to the API.

[andreivladbrg]

Doesn't forge script --verify implies forge script and forge verify-contract under the hood?

yes, most likely.

the problem here is that the block explorer takes a couple of seconds to fetch all the data from the chain. although the contract is deployed, the API call doesn’t recognize it immediately, which would throw this error:
Warning: Etherscan could not detect the deployment. ("X" tries remaining)

if we deploy all contracts first and then verify them, it is very likely that sufficient time will have passed for the block explorer to fetch the data, e.g.:

1. deploy on arbitrum
2. deploy on optimism
3. deploy on polygon
4. verify on arbitrum
5. verify on optimism
6. verify on polygon

lmk if this makes sense

I have also seen that forge verify-contract command waits for 10-15 seconds before making another request to the API.

interesting, haven't seen it

[smol-ninja]

Thats a good explanation of it. Thanks.