-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Replacing Rainbowkit with Web3Modal #1465
Replacing Rainbowkit with Web3Modal #1465
Conversation
✅ Deploy Preview for fractal-dev ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
} catch (e) { | ||
console.error(e); | ||
try { | ||
open(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The problem of not opening Web3Modal from first attempt happens quite frequently. However, I haven't ever noticed that it doesn't work from 2nd attempt, and this fix works smoothly for me.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So prior to the NextJS removal update. I could not get useWeb3Modal
to work properly within the header, while still calling createWeb3Modal else where in the app. The Header component seem to be getting mounted before the providers were getting set and that function is called. Since it seems to be 'working' now but flaky I wonder if there is something in how we mount our header components that still wonky
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
} catch (e) { | ||
console.error(e); | ||
try { | ||
open(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So prior to the NextJS removal update. I could not get useWeb3Modal
to work properly within the header, while still calling createWeb3Modal else where in the app. The Header component seem to be getting mounted before the providers were getting set and that function is called. Since it seems to be 'working' now but flaky I wonder if there is something in how we mount our header components that still wonky
@Da-Colon I was experiencing issues while trying to connect wallet locally and found some GH discussion that was mentioning using HTTPS local dev server to overcome this problem. That, eventually, worked. |
No, that seems like somewhat known issue with web3modal v3 (the one we are using) and should be fixed with migration to v4 |
Damn, that's right. Our custom RPC node is not picked up. Which in a nutshell should be good, but certainly not at this stage 😄 |
…tml, remove redundant wagmi config
…m install warnings
…useNetworkConfig, update usage of useWeb3Modal
…viem-etc Upgrade wagmi, viem, web3modal
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a couple of comments, but lookin good!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
shipit
edit: not yet
**1) Coinbase Wallet + Brave **
Multisig
**2) SafeUI +WC + Chrome **
Multisig
here's the safe with the issues - https://deploy-preview-1465.app.dev.fractalframework.xyz/daos/0xa719FcC542a59A6C52b4C482e562334bF1aF9828
**3) Metamask + Chrome **
Multisig
Note links to test safes |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, found another thing that should be fixed up as part of the different behaviors of RainbowKit and Web3Modal.
This PR contains following changes:
RainbowKit
withWeb3Modal
Closes #1450
Moving further, we'll have to update
web3Modal
version tov4.x+
together with other web3 libraries (viem, wagmi, etc)Testing