Web3Auth not supproting Monad

Embedded Wallets (Web3Auth)
1
  • **We are trying to use the Web3Auth wallet to connect Safe App for signing multisig transactions, though as we add Monad as a custom chain then try to connect using WalletConnect pasting the url we see an error in console that
    **
    "Error: Non conforming namespaces. approve() namespaces chains don't satisfy required namespaces.
    Required: eip155:143
    Approved: eip155:1,eip155:8453,eip155:137,eip155:56,eip155:42161,eip155:10,eip155:59144,eip155:42220,eip155:43114,eip155:11155111,eip155:84532"
2

Thanks — that error lines up with a WalletConnect namespace mismatch. I pulled the details you already gave and summarized them below so the support team can triage quickly, then I’ll recommend next steps.

Extracted details

  • SDK Details: MetaMask Embedded Wallets (Web3Auth)
  • SDK Version Number: not provided — please share the exact package/version you’re using
  • Platform: not provided — please confirm (web Safe App in browser, mobile webview, etc.)

Error & context (from your message)

  • Error: “Error: Non conforming namespaces. approve() namespaces chains don’t satisfy required namespaces. Required: eip155:143 Approved: eip155:1,eip155:8453,eip155:137,eip155:56,eip155:42161,eip155:10,eip155:59144,eip155:42220,eip155:43114,eip155:11155111,eip155:84532”
  • Context: Using Web3Auth (Embedded Wallets) to connect a Safe App via WalletConnect to sign multisig txns; you added Monad as a custom chain but WalletConnect session approval doesn’t include eip155:143.

What this means

  • WalletConnect v2 uses exact namespaces (e.g., eip155:) in the session request/approval. The dapp (Safe App) requested eip155:143, but the wallet (Web3Auth/Embedded Wallets) returned an approved set that does not include 143. That causes the “Non conforming namespaces” error.
  • In short: the wallet must explicitly support/approve eip155:143 for the session to succeed. Many wallet aggregators (including Embedded Wallets/Web3Auth) do not include every new/custom chain by default.

Immediate checks I recommend

  1. Confirm the correct Monad chain namespace: verify that eip155:143 is indeed the chain ID your Safe App expects for Monad (and not a different ID). If the IDs are mismatched, update the Safe App request.
  2. Confirm your Embedded Wallets / Web3Auth configuration: check whether you can add custom chains (chain id + RPC) in the Web3Auth/Embedded Wallets initialization. If not possible, the wallet will not approve eip155:143.
  3. Try the flow with a wallet known to accept the custom chain (e.g., MetaMask extension/mobile where you manually add the network) to confirm the Safe App + WalletConnect flow works when the wallet supports that chain.

Possible solutions / next steps

  • If Web3Auth supports adding custom chains in its config: add Monad (eip155:143) to the supported chains list and include the RPC info so the wallet can return eip155:143 in approved namespaces.
  • If Web3Auth/Embedded Wallets doesn’t allow adding this chain: request chain support from the provider (Embedded Wallets/Web3Auth). Share the Monad chain details (chainId, RPC URL, chainName) when you file the request.
  • As a workaround for testing, connect with a wallet that already supports Monad (manually added MetaMask browser/mobile) to confirm the Safe App flow.

Useful documentation

If you want me to escalate or prepare this for support, please share the missing fields and any of the following if available:

  • SDK version number you’re using
  • Platform (web / browser and version) or environment where you see the error
  • (If convenient) initialization/login snippets for your Web3Auth/Embedded Wallets setup
  • (Optional) a full browser console screenshot or the WalletConnect session request/response payload (shows requested namespaces)

If you’d like, paste the SDK version + platform now and I’ll prepare a short, formatted support summary you can submit to Embedded Wallets / Web3Auth support.

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 biweekly Office Hours to get this resolved even faster. MetaMask Developer Office Hours

3

As we checked internally and the conversation we had on Telegram, the web3auth integration with Monad works as expected. The torus wallet, ie. wallet.web3auth.io does not support monad at the moment. It is deprecated officially for new usage. It is being maintained for our legacy customers. I’d recommend using MetaMask Wallet.