Support OKX wallet / explicitly surface Keplr errors

[tkporter]

Someone in Discord was having intermittent issues with Keplr wallet. They also had the OKX wallet installed. Sometimes when trying to connect to Keplr, the OKX wallet would silently take precedence. The addresses in the side panel would relate to the OKX wallet addresses despite saying "Keplr" on them. We should:

• Either explicitly support the OKX wallets / show them on the right side as "OKX" and surface to the user there was an error with Keplr
• Just surface errors connecting to Keplr and have the user try again

Context

• Internal thread: https://discord.com/channels/935678348330434570/1176475125235851314/1176481680207400981 & https://discord.com/channels/935678348330434570/935679524534911007/1176501791995723797
• User's report: https://discord.com/channels/935678348330434570/1176469470655545354/1176474934235648000

[jmrossy]

I tested this with the latest wagmi/rainbowkit (branch off https://github.com/hyperlane-xyz/hyperlane-warp-ui-template/pull/89) and I don't see any errors. It's possible this issues was fixed in a recent update.

[jmrossy]

Reopening to further investigate OKX issues

[jmrossy]

I've done some more testing with OKX mixed with other wallets in Chrome:

• OKX has a Set as default wallet setting that is enabled by default
• OKX consistently overrides Metamask; I cannot use Metamask when OKX is enabled
• OKX will impersonate Keplr if Keplr is not enabled/installed
• I cannot repro OKX overriding Keplr or Leap when they're all enabled

So TLDR, I can confirm OKX is willing to masquerade as another wallet but I can't repro the exact issue the user saw. It's possible that some users are clicking the Keplr option without realizing they don't have it installed, causing it to actually connect to OKX instead.

AFAI can tell, there is no way to differentiate from Metamask/Keplr vs OKX when OKX is impersonating those other wallets.

I'm testing with the latest version of all extensions. Maybe this bug requires an older version.

In terms of next steps, if I can't get any a reproduction of the bug, I don't think I can look for workarounds. We could try UX solutions, like forcing a confirmation modal for the user to accept.

Finally, I'll just add that the Warp UI is not the only DApp feeling this pain. There's an EIP that Pedro from WalletConnect has been leading which alleviates it but wallets must each buy-in: https://twitter.com/pedrouid/status/1765822163829862589