Wallet Services exposes no Solana RPC methods on a custom-JWT connection (@web3auth/modal 10.16.0)

Embedded Wallets (Web3Auth)
1

EVM works correctly. Solana is unreachable by every documented route.

Setup: @web3auth/modal 10.16.0, WALLET_CONNECTORS.AUTH + AUTH_CONNECTION.CUSTOM (Firebase JWT). Solana Mainnet and Devnet are both enabled on the project — coreOptions.chains returns all six chains, including 0x65 and 0x67 with correct RPC URLs. defaultChainId is 0x89.

sdk.switchChain({chainId:“0x67”}) resolves successfully. After it, on a live connected session, every Solana JSON-RPC method returns -32601 “Method not found”:
solana_requestAccounts, requestAccounts, solana_accounts, getAccounts, solana_provider_config, solana_signMessage, solana_signTransaction.

Note the last two are the values of DEFAULT_SOLANA_METHODS exported by your own SDK, so the provider is rejecting the methods it declares.

Consequently new SolanaWallet(provider).getAccounts() fails (it calls getAccounts), connection.solanaWallet is undefined, and key export is unavailable on both curves (eth_private_key and solana_privateKey both “method does not exist”), so the getED25519Key derivation is also closed off.

All errors originate from wallet.web3auth.io/v5/assets/SolanaController-*.js via AbstractTorusController.

Question: does Wallet Services support Solana for custom-JWT auth connections in v10.x? If it requires additional configuration, which? If it requires v11, please confirm. A vanilla-JS Solana example would also help — the current quick-starts cover React and Vue only.

1 Like
2

Hello, yes - v10.x should support Solana with WALLET_CONNECTORS.AUTH + AUTH_CONNECTION.CUSTOM, including a Firebase JWT. You should not need v11 solely for that.

Your symptoms suggest a Solana controller/Wallet Services configuration or v10 SDK issue, because:

Solana chains/RPCs are present.
switchChain(“0x67”) succeeds.
Every Solana RPC method returns -32601.
Even the SDK’s own DEFAULT_SOLANA_METHODS are rejected.

So this does not look like a Firebase-JWT limitation.

I would verify the project’s Solana/Wallet Services configuration before upgrading to v11. If that is correct, this looks like a v10 compatibility/implementation issue.

A minimal vanilla-JS AUTH + CUSTOM JWT + Solana example would be useful; the current quick-starts aren’t sufficient for this case