# "Invalid params passed in, Please configure chains for smart accounts on dashboard" **URL:** \ **Category:** Embedded Wallets (Web3Auth)\ **Tags:** web3auth\ **Created:** [March 6, 2026, 8:13am UTC](https://builder.metamask.io/t/invalid-params-passed-in-please-configure-chains-for-smart-accounts-on-dashboard/2949 "2026-03-06T08:13:56Z")\ **Posts on this page:** 15\ **Page:** 1
**Author:** ![marchie](https://yyz1.discourse-cdn.com/flex011/user_avatar/builder.metamask.io/marchie/32/2756_2.png) [@marchie](https://builder.metamask.io/u/marchie)\ **Post date:** [March 6, 2026, 8:13am UTC](https://builder.metamask.io/t/invalid-params-passed-in-please-configure-chains-for-smart-accounts-on-dashboard/2949/1 "2026-03-06T08:13:56Z")
- **Describe your issue or question:** ```auto 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](https://dashboard.web3auth.io) to use these features”“ So not sure what’s going on! Thanks ---
**Author:** ![system](https://canada1.discourse-cdn.com/flex011/uploads/metamaskbuilderhub/original/2X/9/92b599d3131e78cf3d3ff01b80e54d69d266f8df.png) [@system](https://builder.metamask.io/u/system)\ **Post date:** [March 6, 2026, 8:15am UTC](https://builder.metamask.io/t/invalid-params-passed-in-please-configure-chains-for-smart-accounts-on-dashboard/2949/2 "2026-03-06T08:15:02Z")
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](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](https://builder.metamask.io/t/metamask-developer-office-hours/2544/1) ---
**Author:** ![marchie](https://yyz1.discourse-cdn.com/flex011/user_avatar/builder.metamask.io/marchie/32/2756_2.png) [@marchie](https://builder.metamask.io/u/marchie)\ **Post date:** [March 6, 2026, 8:41am UTC](https://builder.metamask.io/t/invalid-params-passed-in-please-configure-chains-for-smart-accounts-on-dashboard/2949/3 "2026-03-06T08:41:42Z")
1. I read for v10 chainConfig is not needed (as told by maharshi [Cannot use main net without upgrading - #12 by maharshi](https://builder.metamask.io/t/cannot-use-main-net-without-upgrading/2684/12) ) ---
**Author:** ![shana](https://avatars.discourse-cdn.com/v4/letter/s/3bc359/32.png) [@shana](https://builder.metamask.io/u/shana)\ **Post date:** [March 6, 2026, 9:31am UTC](https://builder.metamask.io/t/invalid-params-passed-in-please-configure-chains-for-smart-accounts-on-dashboard/2949/4 "2026-03-06T09:31:24Z")
Hi did you try without chain ID as suggested? ---
**Author:** ![marchie](https://yyz1.discourse-cdn.com/flex011/user_avatar/builder.metamask.io/marchie/32/2756_2.png) [@marchie](https://builder.metamask.io/u/marchie)\ **Post date:** [March 6, 2026, 3:26pm UTC](https://builder.metamask.io/t/invalid-params-passed-in-please-configure-chains-for-smart-accounts-on-dashboard/2949/5 "2026-03-06T15:26:16Z")
- 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 …” ---
**Author:** ![shana](https://avatars.discourse-cdn.com/v4/letter/s/3bc359/32.png) [@shana](https://builder.metamask.io/u/shana)\ **Post date:** [March 7, 2026, 7:31am UTC](https://builder.metamask.io/t/invalid-params-passed-in-please-configure-chains-for-smart-accounts-on-dashboard/2949/6 "2026-03-07T07:31:11Z")
Please give us time we are checking internally ---
**Author:** ![marchie](https://yyz1.discourse-cdn.com/flex011/user_avatar/builder.metamask.io/marchie/32/2756_2.png) [@marchie](https://builder.metamask.io/u/marchie)\ **Post date:** [March 7, 2026, 9:10am UTC](https://builder.metamask.io/t/invalid-params-passed-in-please-configure-chains-for-smart-accounts-on-dashboard/2949/7 "2026-03-07T09:10:27Z")
Here is the deployed app: [Create Your Rep](https://rep-web-dev.up.railway.app/en) so you can see the error ---
**Author:** ![shana](https://avatars.discourse-cdn.com/v4/letter/s/3bc359/32.png) [@shana](https://builder.metamask.io/u/shana)\ **Post date:** [March 9, 2026, 8:52am UTC](https://builder.metamask.io/t/invalid-params-passed-in-please-configure-chains-for-smart-accounts-on-dashboard/2949/8 "2026-03-09T08:52:38Z")
Apologies for the wait the team is looking into it, we’ll get back to you as soon as possible ---
**Author:** ![NEConsensys](https://yyz1.discourse-cdn.com/flex011/user_avatar/builder.metamask.io/neconsensys/32/2789_2.png) [@NEConsensys](https://builder.metamask.io/u/NEConsensys)\ **Post date:** [March 9, 2026, 9:48am UTC](https://builder.metamask.io/t/invalid-params-passed-in-please-configure-chains-for-smart-accounts-on-dashboard/2949/9 "2026-03-09T09:48:59Z")
![Screenshot 2026-03-09 at 5.48.07 PM](https://canada1.discourse-cdn.com/flex011/uploads/metamaskbuilderhub/original/2X/5/596fb481e71ba411e36136c4cee9f76d31f9aeff.png) Hi @marchie can you check if you have configured the smart account chains in the bundler & paymaster tab? ---
**Author:** ![marchie](https://yyz1.discourse-cdn.com/flex011/user_avatar/builder.metamask.io/marchie/32/2756_2.png) [@marchie](https://builder.metamask.io/u/marchie)\ **Post date:** [March 9, 2026, 3:08pm UTC](https://builder.metamask.io/t/invalid-params-passed-in-please-configure-chains-for-smart-accounts-on-dashboard/2949/10 "2026-03-09T15:08:29Z")
@NEConsensys yes it’s all setup ![image](https://canada1.discourse-cdn.com/flex011/uploads/metamaskbuilderhub/original/2X/0/09c1a662b0e38654873c93e139a6c409e624f891.png) ![image](https://canada1.discourse-cdn.com/flex011/uploads/metamaskbuilderhub/original/2X/b/b5e668d02c5dfc454a978d0885f5935a3dd5f6c7.png) ---
**Author:** ![NEConsensys](https://yyz1.discourse-cdn.com/flex011/user_avatar/builder.metamask.io/neconsensys/32/2789_2.png) [@NEConsensys](https://builder.metamask.io/u/NEConsensys)\ **Post date:** [March 11, 2026, 12:14am UTC](https://builder.metamask.io/t/invalid-params-passed-in-please-configure-chains-for-smart-accounts-on-dashboard/2949/11 "2026-03-11T00:14:19Z")
@marchie on the bundler and paymaster page can you try clicking save again? ---
**Author:** ![marchie](https://yyz1.discourse-cdn.com/flex011/user_avatar/builder.metamask.io/marchie/32/2756_2.png) [@marchie](https://builder.metamask.io/u/marchie)\ **Post date:** [March 11, 2026, 6:33am UTC](https://builder.metamask.io/t/invalid-params-passed-in-please-configure-chains-for-smart-accounts-on-dashboard/2949/12 "2026-03-11T06:33:44Z")
@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](https://api.web3auth.io/signer-service/api/feature-access?client_id=%E2%80%A6.&network=sapphire_mainnet&is_wallet_service=true&enable_gating=true&is_whitelabel=true) 403 (Forbidden) Though the flow works fine - is this normal? Thanks! ---
**Author:** ![NEConsensys](https://yyz1.discourse-cdn.com/flex011/user_avatar/builder.metamask.io/neconsensys/32/2789_2.png) [@NEConsensys](https://builder.metamask.io/u/NEConsensys)\ **Post date:** [March 11, 2026, 6:49am UTC](https://builder.metamask.io/t/invalid-params-passed-in-please-configure-chains-for-smart-accounts-on-dashboard/2949/13 "2026-03-11T06:49:07Z")
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. ---
**Author:** ![NEConsensys](https://yyz1.discourse-cdn.com/flex011/user_avatar/builder.metamask.io/neconsensys/32/2789_2.png) [@NEConsensys](https://builder.metamask.io/u/NEConsensys)\ **Post date:** [March 11, 2026, 7:13am UTC](https://builder.metamask.io/t/invalid-params-passed-in-please-configure-chains-for-smart-accounts-on-dashboard/2949/14 "2026-03-11T07:13:30Z")
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. ---
**Author:** ![yashovardhan](https://yyz1.discourse-cdn.com/flex011/user_avatar/builder.metamask.io/yashovardhan/32/1526_2.png) [@yashovardhan](https://builder.metamask.io/u/yashovardhan)\ **Post date:** [March 17, 2026, 5:39pm UTC](https://builder.metamask.io/t/invalid-params-passed-in-please-configure-chains-for-smart-accounts-on-dashboard/2949/15 "2026-03-17T17:39:34Z")
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.