[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

[seaona]

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

solana-connect-permissions-nets.mp4

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

Detection stage

During release testing

Version

12.18.0

Build type

None

Browser

Chrome

Operating system

Linux

Hardware wallet

No response

Additional context

No response

Severity

No response

[hesterbruikman]

@vandan can you confirm whether this is a bug or expected behavior?

I suspect the dapp would simply ignore irrelevant networks if it's not a 'multichain dapp'? Might still be an issue from a UX perspective because users might expect only compatible networks and accounts to be shown, but in that case I'd say it's a sev3 as we don't know the evolution of cross-chain dapps yet

[jiexi]

I wouldn't call this intentional exactly. We only will auto select networks for the ecosystem when an account is selected and there aren't any matching networks to support it. If the user goes and deselects those networks after the fact, the accounts without at least one matching network will not be granted. In the case that no accounts are granted, it will appear you are disconnected to both the window.ethereum provider and the solana wallet-standard provider AND possibly the wallet UI itself, BUT technically as long as some networks were granted (even if without accounts) that is valid at the Multichain API level.

We've discussed what the UX should look like in this scenario before, but I believe we settled on this behavior for now

[jiexi]

I'm not sure this is a bug so much as a place that we need to iron out the account <-> network selection relationship. They are treated as independent, but in reality there is a dependency of account to network