By default, ConnectKit surfaces the most popular chains to your users. If you'd like, you can include more networks like Base, Zora, and others.

ConnectKit uses wagmi internally, meaning all the various chains from wagmi are available. All you need to do is provide the chains in your config.

First, make sure to import your preferred chains from wagmi:

import { mainnet, base, zora } from "wagmi/chains";

Then simply include the chains in your config. Make sure to include your own RPC Providers for the various chains you want to support.

Below is an example of an app supporting multiple chains using ConnectKit:

import { mainnet, base, zora } from "wagmi/chains";

import { WagmiProvider, createConfig, http } from "wagmi";
import { getDefaultConfig } from "connectkit";

// Choose which chains you'd like to show
const chains = [mainnet, base, zora];

const config = createConfig(
  getDefaultConfig({
    chains,
    transports: {
      [mainnet.id]: http(mainnet.rpcUrls.default.http[0]), // or your own RPC url
      [base.id]: http(base.rpcUrls.default.http[0]), // or your own RPC url
      [zora.id]: http(zora.rpcUrls.default.http[0]), // or your own RPC url
    },
    ...
  }),
);

<WagmiProvider config={config}>
  ...
</WagmiProvider>

And that's it—users can now choose to connect to any of the networks listed in the chains array.

In the example above, we used three different chains. In the table below you'll find a more extensive list of chains you can add to ConnectKit (which wagmi supports out of the box):