You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: wallets/provider-metamask/readme.md
+10-4Lines changed: 10 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,13 +7,19 @@ More about implementation status can be found [here](../readme.md).
7
7
## Implementation notes/limitations
8
8
9
9
### Group
10
-
11
-
#### 🚧 Solana
12
-
MetaMask supports both **EVM** and **Solana**, but this integration currently supports **only EVM** and **Solana** is under construction.
10
+
MetaMask supports both **EVM** and **Solana**.
13
11
14
12
### Feature
15
13
16
-
All implemented features are working correctly.
14
+
#### ⚠️ Switch Account
15
+
16
+
In MetaMask, you can have only one active account at a time, which may belong to either the Solana or EVM namespace. When you connect to MetaMask, it connects to the currently active account—this account could belong to either namespace. Additionally, MetaMask may also establish a random connection to another account from the opposite namespace.
17
+
18
+
When a user switches accounts in MetaMask, the wallet emits an update event tied to the currently active namespace—either EVM or Solana.
19
+
The switchAccount notification is scoped to that active namespace, meaning only the relevant provider will receive the update.
20
+
21
+
Regardless of which namespace triggers the event, MetaMask always executes transactions using the correct account for the selected chain.
22
+
This ensures consistent behavior and prevents cross-namespace conflicts between Solana and EVM contexts.
0 commit comments