HardhatError: HHE40000: No network with chain id "9876" found.

[wisehalvdan]

Version of Hardhat

3.0.17

What happened?

When using ignitions, there is no way to use chains not supported by viem.

Even if we override the network passed in to network.connect() I think ignition still has some dependency to viem and tries to look for chainid in viem network lists.

It can work by monkey patching the viem but since it is pulled in compiled, patching typescript and adding the new chain is not enough and resulting js files also needs to be monkey patched which defeats the purpose.

Also just passing the custom object in a network.connect() breaks the hardhat usual --network flow and makes scripts / ignitions only work on set chain.

Minimal reproduction steps

const gccnet = {
    id: 9876,
    name: "GCCNET",
    network: "gccnet",
    nativeCurrency: {
        name: "GCC",
        symbol: "GCC",
        decimals: 18,
    },
    rpcUrls: {
        default: {
            http: ["https://gccnet.com"],
        },
    },
    blockExplorers: {
        default: {
            name: "explorer",
            url: "https://gccscanner.com",
        },
    },
};

const gccnetChain = defineChain(gccnet)
const { viem, networkName, ignition } = await network.connect(gccnetChain);
const wallets = await viem.getWalletClients(
    {
        chain: gccnetChain,
    }
);


const wallet = wallets[0];

async function main() {
    console.log(`Deploying to ${networkName}... on wallet ${wallet.account!.address}`);

    const { airdropper } = await ignition.deploy(AirdropperModule);
}

Search terms

No response

[kanej]

Hey, I think the issue here is that network.connect("my-network-in-hardhat-config") expects the name of the network in the hardhat.config.ts or a parameters object.
You are passing in a viem chain descriptor, which network.connect is interpreting as network params but ignoring the unexpected properties.
If you update the networks config in hardhat.config.ts: https://hardhat.org/docs/reference/configuration#network-configuration, then you can use the name of the network config in connect:

const { ignition } = await network.connect("mynetwork");

const { airdropper } = await ignition.deploy(AirdropperModule);

[mrwillis]

This doesn't work actually because it seems that getChain in hardhat-viem still references chains from viem/chains via extractChains which is a hardcoded object effectively.

Is there a solution to this? @kanej

export async function getChain<ChainTypeT extends ChainType | string>(
  provider: EthereumProvider,
  chainType: ChainTypeT,
): Promise<ViemChain> {
  const cachedChain = chainCache.get(provider);
  if (cachedChain !== undefined) {
    return cachedChain;
  }

  const chainId = await getChainId(provider);

  let chain = extractChain({
    chains,
    id: chainId,
  });

  if ((await isDevelopmentNetwork(provider)) || chain === undefined) {
    if (await isHardhatNetwork(provider)) {
      chain = createHardhatChain(provider, chainId, chainType);
    } else if (await isAnvilNetwork(provider)) {
      chain = {
        ...anvil,
        id: chainId,
      };
    } else if (chain === undefined) {
      // If the chain couldn't be found and we can't detect the development
      // network we throw an error.
      throw new HardhatError(
        HardhatError.ERRORS.HARDHAT_VIEM.GENERAL.NETWORK_NOT_FOUND,
        {
          chainId,
        },
      );
    } else {
      assertHardhatInvariant(
        false,
        "This should not happen, as we check in isDevelopmentNetwork that it's either hardhat or anvil",
      );
    }
  }

  chainCache.set(provider, chain);

  return chain;
}

[kanej]

This doesn't work actually because it seems that getChain in hardhat-viem still references chains from viem/chains via extractChains which is a hardcoded object effectively.

Is there a solution to this? @kanej

export async function getChain<ChainTypeT extends ChainType | string>(
provider: EthereumProvider,
chainType: ChainTypeT,
): Promise {
const cachedChain = chainCache.get(provider);
if (cachedChain !== undefined) {
return cachedChain;
}

const chainId = await getChainId(provider);

let chain = extractChain({
chains,
id: chainId,
});

if ((await isDevelopmentNetwork(provider)) || chain === undefined) {
if (await isHardhatNetwork(provider)) {
chain = createHardhatChain(provider, chainId, chainType);
} else if (await isAnvilNetwork(provider)) {
chain = {
...anvil,
id: chainId,
};
} else if (chain === undefined) {
// If the chain couldn't be found and we can't detect the development
// network we throw an error.
throw new HardhatError(
HardhatError.ERRORS.HARDHAT_VIEM.GENERAL.NETWORK_NOT_FOUND,
{
chainId,
},
);
} else {
assertHardhatInvariant(
false,
"This should not happen, as we check in isDevelopmentNetwork that it's either hardhat or anvil",
);
}
}

chainCache.set(provider, chain);

return chain;
}

That is interesting, can I check I am following. You deploy using Ignition with the viem plugin. The deployment succeeds against the network, but because the chain is not available in viem, when Ignition creates contract instances for the deployed contracts it throws a NETWORK_NOT_FOUND error.

@schaable is there a better fallback behavior that Ignition should be using here?

[mrwillis]

Yea the issue is just the extractChains function. You can see it references the hard-coded list, which doesn't contain the custom network.

https://github.com/wevm/viem/blob/main/src/utils/chain/extractChain.ts

So there needs to be a way to add your chain in the plugin. I think this issue should be re-opened