This repository was archived by the owner on Apr 10, 2025. It is now read-only.
Connecting with wrong network #158
Assignees
Labels
Comments
VanishMax
added a commit
that referenced
this issue
Jan 16, 2025
github-project-automation
bot
moved this from 🏗 In progress
to ✅ Done
in Penumbra Web + Not Web
TalDerei
pushed a commit
to penumbra-zone/web
that referenced
this issue
Mar 10, 2025
…t is on wrong chain and disconnect (github.com/penumbra-zone/dex-explorer/issues/274)
TalDerei
pushed a commit
to penumbra-zone/web
that referenced
this issue
Mar 25, 2025
…ng chain and disconnect (penumbra-zone/dex-explorer/issues/274)
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We currently have a function called walletOnWrongChain. It is able to detect if a Prax connection has a different chain ID than what the interface supports (e.g. Prax is on testnet, but trading interface + db is for mainnet).
The function is used in some queries and throwing (but I'm not seeing those "wrong wallet" errors in the UI as I'd expect 🤔). Whenever attempts a connection and we detect the wrong network, we can simply use the browser default
alert()to give a message and trigger a wallet disconnect after it's dismissed.The text was updated successfully, but these errors were encountered: