Verification with custom chain config

[nvitorovic]

What happened?

I attempted to add a custom chain using Tenderly Virtual TestNets with chain ID 73571 (made up ID). Deployment went on, but verification failled. The custom chain shows up on the list npx hardhat verify --list-networks. I get

Verification not natively supported for chainId 73571. Please use a custom chain configuration to add support.

Minimal reproduction steps

1. Added the following to hardhat.config.ts, per docs

const config: HardhatUserConfig = {
  solidity: "0.8.27",
  networks: {
    tenderly_ci: {
      url: process.env.TENDERLY_ADMIN_RPC_URL,
      chainId: parseInt(process.env.TENDERLY_CHAIN_ID!)
    },
  },
  etherscan: {
    apiKey: {
      tenderly_ci: process.env.TENDERLY_ACCESS_KEY!
    },
    customChains: [
      {
        network: "tenderly_ci",
        // here
        chainId: parseInt(process.env.TENDERLY_CHAIN_ID!),
        urls: {
          apiURL: `${process.env.TENDERLY_ADMIN_RPC_URL}/verify/etherscan`,
          browserURL: process.env.TENDERLY_ADMIN_RPC_URL!
        }
      }
    ]
  },
  tenderly: {
    project: process.env.TENDERLY_PROJECT_NAME!,
    username: process.env.TENDERLY_ACCOUNT_NAME!,
    accessKey: process.env.TENDERLY_ACCESS_KEY!
  },
  sourcify: {
    enabled: false
  }
};

2. npx hardhat verify --list-networks works
3. yes | npx hardhat ignition deploy ./ignition/modules/Lock.ts --network tenderly_ci --deployment-id test - contract gets deployed, errors with

Verification not natively supported for chainId 73571. Please use a custom chain configuration to add support.

Search terms

tenderly verification

[kanej]

Hey @nvitorovic, Ignition and hardhat-verify are separate plugins (though hardhat-verify`), so there may be an issue in Ignition's wrapping code.
Taking a look, Ignition throws that error if the lookup on custom chains fails.
If the chain id under custom chains is hard coded to 73571, do you get a different error?

Can I ask more generally have you been able to verify against Tenderly virtual nets, say using hardhat-verify?