Wagmi not using the provider provided?

[johnpaulcas]

Hello, We are experiencing an issue where users who connect to 'wagmi' are not directed to the Alchemy RPC provider that we configured. Instead, they are being connected to the default RPC provider, which is https://matic-mumbai.chainstacklabs.com/.

1. Can you confirm if our configuration for using the Alchemy RPC provider with 'wagmi' is functioning correctly?

2. How can we debug and determine which configuration 'wagmi' is using when initiating transactions? Specifically, we want to know if it's using the settings from MetaMask or the custom RPC provider we have set up.

This is our config

import { getDefaultConfig } from 'connectkit'
import { configureChains, createConfig } from 'wagmi'
import { publicProvider } from 'wagmi/providers/public'

import { InjectedConnector } from 'wagmi/connectors/injected'
import { MetaMaskConnector } from 'wagmi/connectors/metaMask'

import { polygon, polygonMumbai } from 'wagmi/chains'
import { alchemyProvider } from 'wagmi/providers/alchemy'

const alchemyKey = process.env.NEXT_PUBLIC_ALCHEMY_KEY || ''
const envName = process.env.NEXT_PUBLIC_APP_ENV || ''

const supportedNetwork = envName === 'production' ? polygon : polygonMumbai

const { chains, publicClient, webSocketPublicClient } = configureChains(
  [supportedNetwork],
  [alchemyProvider({ apiKey: alchemyKey }), publicProvider()],
  { stallTimeout: 5_000, retryCount: 5, retryDelay: 5, rank: true }
)

export const config = createConfig(
  getDefaultConfig({
    autoConnect: true,
    appName: 'DApps',
    walletConnectProjectId: '', 
    publicClient,
    webSocketPublicClient,
    connectors: [
      new MetaMaskConnector({ chains }),
      new InjectedConnector({
        chains,
        options: {
          name: 'Injected',
          shimDisconnect: true,
        },
      }),
    ],
  })
)

FYI: we are using wagmi/actions

Thank you

[thomasvalera]

I have the same issue, did you solve it? @johnpaulcas

[Diego-c22]

I have the same issue, did you solve it? @johnpaulcas @thomasvalera

[Diego-c22]

The solution I found is to add Mumbai as custom chain, making use of a jsonRpcProvided. Here is an implementation.

Chain

import { Chain } from "wagmi";

export const mumbai = {
  id: 80_001,
  name: "Mumbai",
  network: "Mumbai",
  nativeCurrency: {
    decimals: 18,
    name: "MATIC",
    symbol: "MATIC",
  },
  rpcUrls: {
    public: { http: [mumbaiRPC},
    default: { http: [mumbaiRPC] },
  },
  blockExplorers: {
    etherscan: { name: "PolygonScan", url: "https://mumbai.polygonscan.com/" },
    default: { name: "PolygonScan", url: "https://mumbai.polygonscan.com/" },
  },
} as const satisfies Chain;

Configure chain

const { chains, publicClient, webSocketPublicClient } = configureChains(
  [mumbai, polygon],
  [
    alchemyProvider({ apiKey: API_KEY }),
    jsonRpcProvider({
      rpc: (chain) => ({
        http: chain.id === 80_001 ? mumbaiRPC : polygonRPC,
      }),
    }),
  ],
);