fix chains not configured buggst

scaffold-eth · Feb 17, 2024 · b6f406a · b6f406a
1 parent c454a41
commit b6f406a
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 2 deletions.
diff --git a/packages/nextjs/hooks/scaffold-eth/useAccountBalance.ts b/packages/nextjs/hooks/scaffold-eth/useAccountBalance.ts
@@ -11,7 +11,7 @@ export function useAccountBalance(address?: Address) {
   const price = useGlobalState(state => state.nativeCurrencyPrice);
   const { targetNetwork } = useTargetNetwork();
 
-  const { data: blockNumber } = useBlockNumber({ watch: true });
+  const { data: blockNumber } = useBlockNumber({ watch: true, chainId: targetNetwork.id });
   const {
     data: fetchedBalanceData,
     isError,

diff --git a/packages/nextjs/services/web3/wagmiConfig.tsx b/packages/nextjs/services/web3/wagmiConfig.tsx
@@ -1,4 +1,4 @@
-import { enabledChains } from "./wagmiConnectors";
+import { enabledChains, wagmiConnectors } from "./wagmiConnectors";
 import { createClient, http } from "viem";
 import { hardhat } from "viem/chains";
 import { createConfig } from "wagmi";
@@ -7,6 +7,7 @@ import scaffoldConfig from "~~/scaffold.config";
 export const wagmiConfig = createConfig({
   // TODO: Maybe we should get literal value here currently TS has widened the types because of ensabledChains logic
   chains: enabledChains,
+  connectors: wagmiConnectors,
   ssr: true,
   client({ chain }) {
     return createClient({