feat: Migrate to walletconnect v2 using ethereum-provider #3581
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR prepares the WalletConnect v2 integration to be deployed as a bug fix (expected v1 sunset date is Wed 28).
Walletconnect team confirmed that there are still some issues with Metamask wallet when switching networks. (They are working on that).
Switched walletconnect/web3-provider to walletconnect/ethereum-provider. This is v2 of walletconnect which changes the modal and connection url format.
Type of change
How should this be tested?
Please provide instructions so we can test. Please also list any relevant details for your test configuration.
Visual context
Please provide any relevant visual context for UI changes or additions. This could be static screenshots or a loom screencast.
Checklist:
master
if hotfix,develop
if not