Replies: 3 comments 4 replies
-
Totally agree with this suggestion: Right now, if the user's wallet is connected and has a network selected that's unsupported by the page's wagmi client, connectkit pops up a modal that forces the user to change their wallet's active network to a supported network. Today, this modal can't be dismissed or configured. For various UX reasons and use cases, this modal should be dismissable and configurable to be disabled. As a detail, connectkit should likely have no reliance on the rpc endpoint associated with the user's connected wallet's current active network because it should use only rpc endpoints provided to the wagmi client. So, afaict, there should be no technical blocker in simply ignoring whatever network the user's wallet current has active until later in the UX (eg. transaction signing). |
Beta Was this translation helpful? Give feedback.
-
I believe this is possible by setting <ConnectKitProvider options={{ initialChainId: 0 }}> see: https://docs.family.co/connectkit/api-reference#ConnectKitProvider-initialChainId |
Beta Was this translation helpful? Give feedback.
-
Have started a PR regarding this! |
Beta Was this translation helpful? Give feedback.
-
Usually the user's connected Network doesn't matter up to the point he decides to take some on-chain action. This is the case on mint pages, for instance, where the user should be able to check the artwork, read a bit of the details, and then just be prompted to switch Networks when the time to mint comes.
Having the switch network prompt pop up when the page is open is disruptive.
It would be great to have the option to prompt for a Network change only when the user tries to use their wallet to sign something, instead of whenever the user is connected to the dapp
Beta Was this translation helpful? Give feedback.
All reactions