MetaMask / MetaMask/metamask-extension
[Bug]: EVM vs non EVM permissions - I am able to select Solana Accounts with EVM networks and EVM accounts with Solana networks on the Connect Screen
- Dominant language
- TypeScript
- Stars
- 13.2k
- Forks
- 5.6k
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 451
Description
**Describe the bug**
I am able to select Solana Accounts with EVM networks and EVM accounts with Solana networks on the Connect Screen. If I proceed nothing happens (I Remain disconnected), which seems expected.
**Expected behavior**
It seems we are missing some logic here, as the UI allows me to proceed with incompatible combinations of EVM/nonEVM accounts vs EVM/nonEVM networks. Nothing happens after proceeding (I remain disconnected from the dapp).
It might be good to prevent this at the UI level.
**Screenshots/Recordings**
https://github.com/user-attachments/assets/accc5fc2-ee56-4610-9319-6a7be1191b87
**Steps to reproduce**
1. Go to any dapp
2. Click Connect
3. See it's possible to Select EVM Account with non EVM netowrk and vice-versa (improvement here?)
4. Nothing happens after accepting (Expected)
**Error messages or log output**
```shell
```
**Detection stage**
During release testing
**Version**
12.18.0
**Build type**
None
**Browser**
Chrome
**Operating system**
Linux
Contributor guide
Research direction
Start at the Connect screen's account and network selection flow and reproduce the incompatible EVM/non-EVM combinations described in the issue. Done means the UI prevents or otherwise blocks incompatible account-network selections before accepting the connection, with compatible selections still proceeding normally.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- blockchain, frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100