"Invalid params passed in, Please configure chains for smart accounts on dashboard"

[marchie]

• Describe your issue or question:

  • Framework: NextJS

  • SDKs used: “@web3auth/ethereum-provider”: “^9.7.0”; “@web3auth/no-modal”: “^10.14.0”; “@web3auth/openlogin-adapter”: “^8.12.4”,?

  • On load I get this error:
    71cef74e7b115971.js:1 Error: Invalid params passed in, Please configure chains for smart accounts on dashboard at https://dashboard.web3auth.io
    at p (71cef74e7b115971.js:1:25689)
    at l.error (71cef74e7b115971.js:1:28722)Caused by: WalletInitializationError: Invalid params passed in, Please configure chains for smart accounts on dashboard at https://dashboard.web3auth.io

    I have Base Mainnet selected under Chains & Networks, and Smart Accounts are enabled (with Metamask and Embedded wallets only

  • This only happens with sapphire_mainnet. Devnet + base-sepolia works fine

  • I have the Growth plan

    const init = async () => {
      try {
         setUiState("initializing");
         const web3auth = new Web3AuthNoModal({
            clientId,
            web3AuthNetwork,
            /* chains */
         });
      await web3auth.init();
    ...

I had chains = [chainConfig] with which the behavior was different - the console error on load was:
”“The current subscription plan is growth and requesting features (wallet service) are not available on base plan. Please upgrade to a higher plan at https://dashboard.web3auth.io to use these features”“

So not sure what’s going on!

Thanks

[system]

Looks like an Embedded Wallets / Web3Auth config issue (not a MetaMask SDK bug). Quick checklist to fix the “Invalid params… configure chains for smart accounts” error:

1. Dashboard: In https://dashboard.web3auth.io → your project → Smart Accounts, confirm sapphire_mainnet is added, enabled, saved, and that Embedded/MetaMask wallets are allowed for that chain.
2. Code: ensure you pass a matching chainConfig to Web3AuthNoModal (chainNamespace: “eip155”, chainId as the exact hex Web3Auth expects, rpcTarget, displayName, ticker). Example: { chainNamespace: “eip155”, chainId: “0x…”, rpcTarget: “https://…”, displayName: “Sapphire Mainnet” }. chainId must match the dashboard entry exactly.
3. Plan limits: Growth may not permit smart-account features on some mainnets (Sapphire mainnet could require a higher plan). If dashboard + code are correct but error persists, contact Web3Auth support or check plan details.

If it still fails, paste the exact chainConfig object you’re passing (and a screenshot of the Smart Accounts list if you can) and I’ll review it.

Note: This response was generated by an AI bot and may require further verification. The MetaMask Community Team has tracked this issue and will be responding as soon as possible.

Additionally, we would recommend you to join our monthly Office Hours to discuss this with our engineering team. MetaMask Developer Office Hours

[marchie]

2. I read for v10 chainConfig is not needed (as told by maharshi Cannot use main net without upgrading - #12 by maharshi )

[shana]

Hi did you try without chain ID as suggested?

[marchie]

• Without chainConfig => “WalletInitializationError: Invalid params passed in…”

• With chainConfig => “The current subscription plan is growth and requesting features (wallet service) are not available on growth …”

[shana]

Please give us time we are checking internally

[marchie]

Here is the deployed app: Create Your Rep so you can see the error

[shana]

Apologies for the wait the team is looking into it, we’ll get back to you as soon as possible

[NEConsensys]

Hi @marchie can you check if you have configured the smart account chains in the bundler & paymaster tab?

[marchie]

@NEConsensys yes it’s all setup

[NEConsensys]

@marchie on the bundler and paymaster page can you try clicking save again?

[marchie]

@NEConsensys
I saved and it seems to be working fine!
I think it should be explicitly stated that you need to save, for future users.
One more question: onLoad I get this error in the console:index-CQouAA6A.js:5 GET https://api.web3auth.io/signer-service/api/feature-access?client_id=….&network=sapphire_mainnet&is_wallet_service=true&enable_gating=true&is_whitelabel=true 403 (Forbidden)

Though the flow works fine - is this normal?

Thanks!

[NEConsensys]

Actually after trying out your deployed demo app it seems everything is working as expected. I think u can safely ignore the feature access error.

[NEConsensys]

Yes, it’s fine just ignore it. And as for the part about informing users to save you are right I am creating a task to work on it.

[yashovardhan]

Hey there

Can you please delete the packages openlogin and ethereum provider? They might be conflicting here since the versions are mismatching the latest one. Just the no-modal package is enough.