upgrades the web3modal to v2, which introduces a whole new approach through the use of the wagmi package that provides various React hooks like useAccount(), useSigner(), etc. Requests that are made with the provider will now appear in the network tab
removes the ENS name lookups from the proposal load (they were responsible for creating over 300 requests on the History page). Instead we do some preloading of the proposal creator, and defer the ENS name lookups for the target address and parameters (loaded on the Proposal Details page)
removes the switch account code that I believe was there only for Hardhat. It requires more effort to implement which doesn't seem worth it at this stage
makes use of more JS bundles (the use of web3modal/react package results in an async chunk/bundle)
adds test utils that creates a mock wagmi client
Outstanding question:
Do we still need to support Rinkeby? wagmi deprecated Rinkeby a while ago and doesn't export the chain anymore.
Edit:Answer: No, we don't support Rinkeby anymore. I've logged #414 to remove Rinkeby
Resolves #401
What does this change?
wagmipackage that provides various React hooks likeuseAccount(),useSigner(), etc. Requests that are made with theproviderwill now appear in the network tabweb3modal/reactpackage results in an async chunk/bundle)Outstanding question: Do we still need to support Rinkeby?
wagmideprecated Rinkeby a while ago and doesn't export the chain anymore. Edit: Answer: No, we don't support Rinkeby anymore. I've logged #414 to remove RinkebyScreenshots