Migrate MetaMask Connector to use new SDK (MMConnect) by adonesky1 · Pull Request #2326 · Web3Auth/web3auth-web

adonesky1 · 2026-01-07T22:37:30Z

Summary

Migrate MetaMask integration from @metamask/sdk to @metamask/connect-evm for improved connection handling
Refactor MetaMaskConnector to use the new SDK's createEVMClient() API with built-in event handlers and automatic chain management
Remove manual chain addition logic as the new SDK handles this internally during switchChain()
Update connector settings interface to align with the new SDK's configuration options

Videos

Extension:
https://drive.google.com/file/d/1r_lDBvwHWQhP-J4yFfqVHsqRR7bIS6Z1/view?usp=sharing

Mobile (native browser):
https://drive.google.com/file/d/1XECLgCOqa9VEeIK4gp1nUf0cs6RRg2V1/view?usp=sharing

Note

Medium Risk
Mostly dependency/lockfile churn, but it changes wallet-connection plumbing (MetaMask SDK dependency swap) and alters Solana wsTarget handling, which can affect runtime connectivity.

Overview
Updates the demo apps to newer @web3auth/* package versions (notably bumping @web3auth/no-modal and @web3auth/modal) and refreshes the associated dependency graph in package-lock.json, including replacing @metamask/sdk with @metamask/connect-evm and bumping several wallet/chain libs.

In the Vue demo, rpcUrlToWsUrl no longer converts HTTPS RPC URLs to WSS (it now returns the provided URL as-is), and the Vite dev server is configured with host: true to allow external network access.

^{Written by Cursor Bugbot for commit 36479eb. This will update automatically on new commits. Configure here.}

vercel · 2026-01-07T22:37:35Z

@adonesky1 is attempting to deploy a commit to the Consensys Team on Vercel.

A member of the Team first needs to authorize it.

demo/vue-app-new/src/services/ethHandlers.ts

demo/vue-app-new/src/utils/constants.ts

jiexi · 2026-01-20T21:51:17Z

packages/no-modal/src/connectors/metamask-connector/metamaskConnector.ts

+      this.metamaskInstance = await this.metamaskPromise;
+      // TODO: Remove this hack
+      // Hack to ensure the ConnectEvm instance has fully resumed the connection
+      await new Promise((resolve) => setTimeout(resolve, 2000));


Note this awful delay to ensure that this async call in the ConnectEvm constructor has fully resolved. We need to fix this on the connect-monorepo side

What is your understanding of how we resolve this on the connect-evm side of things?

Ticket to resolve this here: https://consensyssoftware.atlassian.net/browse/WAPI-1035?atlOrigin=eyJpIjoiMjk1OGRjZjE3MjcwNDQyMzhjODdmMjU3MTMyMDdhMmEiLCJwIjoiaiJ9

we need to release connect-evm again, bump the version in web3auth, and then remove this setTimeout

jiexi · 2026-01-20T21:52:15Z

packages/no-modal/src/connectors/metamask-connector/metamaskConnector.ts

+      // if (options.autoConnect) {
+      //   this.rehydrated = false;
+      //   this.emit(CONNECTOR_EVENTS.REHYDRATION_ERROR, new Error("Failed to resume existing MetaMask Connect session.") as Web3AuthError);
+      // } else {


i think this commented code can be dropped?.. Not sure if it's more appropriate to throw an error if we fail to resume a previous session OR if we just say the connector is ready for new connections

I would think it makes more sense to just say the connector is ready for new connections. But perhaps we should speak with @chaitanyapotti to see what patterns they recommend for their connectors

packages/no-modal/src/connectors/metamask-connector/metamaskConnector.ts

jiexi · 2026-01-20T22:29:09Z

Need: MetaMask/connect-monorepo#124

jiexi · 2026-01-27T22:05:58Z

packages/no-modal/src/connectors/metamask-connector/metamaskConnector.ts

+/**
+ * Configuration options for the MetaMask connector using @metamask/connect-evm
+ */
+export interface MetaMaskConnectorSettings {
+  /** Dapp identification and branding settings */
+  dapp?: {
+    name?: string;
+    url?: string;
+  };
+  /** Enable debug logging for the MetaMask SDK */
+  debug?: boolean;
+}

 export interface MetaMaskConnectorOptions extends BaseConnectorSettings {
-  connectorSettings?: Partial<MetaMaskSDKOptions>;
+  connectorSettings?: MetaMaskConnectorSettings;


reminder to document this breaking change and include migration instructions where appropriate

packages/no-modal/src/connectors/metamask-connector/metamaskConnector.ts

tuna1207 · 2026-01-29T15:01:20Z

packages/no-modal/src/connectors/metamask-connector/metamaskConnector.ts

+    for (const chain of this.coreOptions.chains) {
+      // Convert hex chainId (0x1) to number for CAIP-2 format (eip155:1)
+      const numericChainId = parseInt(chain.chainId, 16);
+      const caipChainId = `eip155:${numericChainId}`;


we can use this ready made getCaipChainId util for getting caipChainId similar to

web3auth-web/packages/no-modal/src/connectors/metamask-connector/metamaskConnector.ts

Line 134 in 3286675

chain_id: getCaipChainId(chainConfig),

chaitanyapotti · 2026-02-02T11:35:25Z

packages/no-modal/src/noModal.ts

-      // only set headless to true if modal SDK is used, otherwise just use the modal from native Metamask SDK
-      connectorFns.push(metaMaskConnector(modalMode ? { headless: true } : undefined));
+      // Note: The new @metamask/connect-evm SDK handles its own UI internally
+      connectorFns.push(metaMaskConnector());


we ideally can't use the metamask sdk ui since the ux would be very different. is there no option for headless mode?

good point. thank you for the call out efd18ff

chaitanyapotti · 2026-02-02T11:36:34Z

packages/no-modal/src/connectors/metamask-connector/metamaskConnector.ts

+    const appUrl = this.connectorSettings?.dapp?.url || window.location.origin || "https://web3auth.io";
+
+    // Initialize the MetaMask Connect EVM SDK
+    this.metamaskPromise = createEVMClient({


how do we support solana?

we should switch the client based on active chain / use multi-chain client and switch chain in this connector based on active chain in sdk

packages/no-modal/src/connectors/metamask-connector/metamaskConnector.ts

cursor · 2026-03-04T21:01:17Z

packages/no-modal/src/connectors/metamask-connector/metamaskConnector.ts

+    const supportedNetworks: Record<string, string> = {};
+    for (const chain of this.coreOptions.chains) {
+      supportedNetworks[chain.chainId] = chain.rpcTarget;
+    }


Supported networks use hex IDs instead of CAIP-2 format

Medium Severity

The comment states the supportedNetworks map uses CAIP-2 format keys (eip155:chainId), but the code uses chain.chainId directly (hex format like 0x1). The imported getCaipChainId utility — used correctly elsewhere in this file for analytics — is not applied here. If @metamask/connect-evm expects CAIP-2 keys, the SDK won't recognize any of the configured networks.

cursor

Cursor Bugbot has reviewed your changes and found 1 potential issue.

cursor · 2026-03-04T21:17:20Z

demo/vue-app-new/src/utils/constants.ts

-  return rpcUrl.replace("https://", "wss://");
+  // if (!rpcUrl) throw new Error("Please configure https endpoint for solana rpc");
+  // return rpcUrl.replace("https://", "wss://");
+  return rpcUrl;


WebSocket URL conversion commented out, wsTarget gets wrong protocol

Medium Severity

The rpcUrlToWsUrl function has had its validation and URL conversion logic commented out and now just returns the input URL unchanged. This means the wsTarget fields in all three Solana network configurations (mainnet, testnet, devnet) will contain https:// URLs instead of wss:// WebSocket URLs. The function name still implies a protocol conversion that no longer happens. This looks like a temporary debugging change that was accidentally included in the commit.

adonesky1 added 3 commits January 7, 2026 16:04

migrate metamask connector to new sdk

6fbe545

package update

159a350

wip

67013a6

adonesky1 marked this pull request as draft January 7, 2026 23:03

adonesky1 and others added 3 commits January 8, 2026 14:52

more working

8d67eaf

more working

52bafcb

Fix metamask connector

288a667

jiexi mentioned this pull request Jan 20, 2026

fix: Fix eth_chainId not being resolved from cache when using EIP-1193 Provider MetaMask/connect-monorepo#124

Merged

4 tasks

jiexi reviewed Jan 20, 2026

View reviewed changes

demo/vue-app-new/src/services/ethHandlers.ts Outdated Show resolved Hide resolved

jiexi reviewed Jan 20, 2026

View reviewed changes

demo/vue-app-new/src/utils/constants.ts Outdated Show resolved Hide resolved

jiexi reviewed Jan 20, 2026

View reviewed changes

packages/no-modal/src/connectors/metamask-connector/metamaskConnector.ts Outdated Show resolved Hide resolved

jiexi and others added 10 commits January 22, 2026 12:44

use connect-evm 0.3.0

114cfbd

fix package lock

17e1c44

adopt ConnectEvm.status change

054ad3f

Merge remote-tracking branch 'origin' into ad/migrate-metamask-connector

f3ce613

update package-lock.json

ea7e070

connect-evm bump

dda7b97

package-lock

8e4a2c8

Merge remote-tracking branch 'origin' into ad/migrate-metamask-connector

0eac6bb

cleanup

b9c977a

more cleanup

24e210d

adonesky1 changed the title ~~Update metamask connector WIP~~ Migrate MetaMask Connector to use new SDK (MMConnect) Jan 23, 2026

adonesky1 marked this pull request as ready for review January 23, 2026 22:34

jiexi reviewed Jan 27, 2026

View reviewed changes

jiexi added 2 commits January 27, 2026 15:20

bump connect-evm 0.4.1

5379c92

remove timeout hack

87da4b7

cursor bot reviewed Jan 27, 2026

View reviewed changes

packages/no-modal/src/connectors/metamask-connector/metamaskConnector.ts Outdated Show resolved Hide resolved

tuna1207 reviewed Jan 29, 2026

View reviewed changes

chaitanyapotti reviewed Feb 2, 2026

View reviewed changes

jiexi added 5 commits March 4, 2026 12:57

bump connect-evm to 0.5.0

49ba588

Fix hex chain id usage

e56eb7f

add iconUrl support

02da6c9

expose UI options

b2dacdf

add display_uri

76625eb

cursor bot reviewed Mar 4, 2026

View reviewed changes

jiexi added 2 commits March 4, 2026 13:14

make sure no UI is shown

efd18ff

revert this before merge

36479eb

cursor bot reviewed Mar 4, 2026

View reviewed changes

Conversation

adonesky1 commented Jan 7, 2026 • edited by cursor bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Videos

Uh oh!

vercel bot commented Jan 7, 2026

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

jiexi commented Jan 20, 2026

Uh oh!

jiexi Jan 27, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

cursor bot Mar 4, 2026

Choose a reason for hiding this comment

Supported networks use hex IDs instead of CAIP-2 format

Uh oh!

cursor bot left a comment

Choose a reason for hiding this comment

Uh oh!

cursor bot Mar 4, 2026

Choose a reason for hiding this comment

WebSocket URL conversion commented out, wsTarget gets wrong protocol

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

adonesky1 commented Jan 7, 2026 •

edited by cursor bot

Loading

jiexi Jan 27, 2026 •

edited

Loading