feat(forge): allow --verifier custom option

[grandizzy]

Motivation

Closes #9220
Closes #8254
Closes #7466 (no need to pass chain param as it will be retrieved from provider / --rpc-url)
Closes #8100

• allows custom verifiers to be defined as --verifier custom. adds --verifier-api-key for custom verifier keys

Verifier options:
      --verifier <VERIFIER>
          The contract verification provider to use
          
          [default: etherscan]

          Possible values:
          - etherscan
          - sourcify
          - blockscout
          - oklink
          - custom:     Custom verification provider, compatible with Etherscan API

      --verifier-api-key <VERIFIER_API_KEY>
          The verifier API KEY, if using a custom provider
          
          [env: VERIFIER_API_KEY=]

      --verifier-url <VERIFIER_URL>
          The verifier URL, if using a custom provider
          
          [env: VERIFIER_URL=]

• could be passed as cli arg, e.g.

forge create \
  --rpc-url http://localhost:8545 \
  --private-key 0x12345.... \
  src/Counter.sol:Counter \
  --verify \
  --verifier custom \
  --verifier-url http://localhost:8888/api \
  --verifier-api-key 1234

forge verify-contract \
  0x59b670e9fA9D0A427751Af201D676719a970857b \
  --rpc-url http://localhost:8545 \
  --verifier custom \
  --verifier-url http://localhost:8888/api \
  --verifier-api-key 1234

or defined and implicitly taken from foundry.toml config, e.g.

[etherscan]
anvil-hardhat = { key = "1234", url = "http://localhost:8888/api" }

forge create \
  --rpc-url http://localhost:8545 \
  --private-key 0x12345.... \
  src/Counter.sol:Counter \
  --verify

forge verify-contract \
  0x59b670e9fA9D0A427751Af201D676719a970857b \
  --rpc-url http://localhost:8545

• better user feedback for retry error handle, print console warning

Solution

[grandizzy]

I think would be nice to have a --verifier-api-key so custom verifiers args won't need the etherscan keyword at all...

foundry/crates/verify/src/verify.rs

Line 36 in 54ea38d

pub verifier_url: Option<String>,

[d-democrazy]

Having hardtime to verify contract on Core Testnet (EVM Compatible)
Testnet chain details:

1. Chain ID: 1115
2. RPC URL: https://rpc.test.btcs.network/
3. Endpoint URL: https://api.test.btcs.network/
4. Block explorer: https://scan.test.btcs.network/

CLI Command:
forge verify-contract 0xAC11A1fB819261c4015b94A50dEDC7683a01aB13 --rpc-url $CORE_TESTNET_RPC_URL --verifier custom --verifier-url https://api.test.btcs.network/api --verifier-api-key $CORE_TESTNET_API_KEY

Respond:

[⠊] Compiling...
No files changed, compilation skipped
Start verifying contract `0xAC11A1fB819261c4015b94A50dEDC7683a01aB13` deployed on 1115
2024-11-25T09:01:47.243277Z ERROR etherscan: Failed to deserialize response: data did not match any variant of untagged enum ResponseData res="{\"status\":401,\"error\":\"Unauthorized\",\"message\":\"401 Permission Verification Failed. This apikey is illegal!\"}"
Error: Failed to deserialize content: data did not match any variant of untagged enum ResponseData
{"status":401,"error":"Unauthorized","message":"401 Permission Verification Failed. This apikey is illegal!"}

Api key checking:
curl -X GET "https://api.test.btcs.network/api?module=account&action=balance&address=0x0000000000000000000000000000000000000000&apikey=27a066b93107401a81d635da00c0fa09

Respond:
{"status":"1","result":203867733802160000000000,"message":"OK"}

[grandizzy]

@d-democrazy looks like Block explorer is not etherscan API compatible, so not much we could do here, custom verifiers requires such - custom: Custom verification provider, compatible with Etherscan API