Multichain support for Walletconnect v2 #184
-
|
Walletconnect v2 now allows you to connect a wallet to multiple chains at the same time, and then to make tx request and choose in the request which chain is intended to. This is not possible when wrapping the Walletconnect universal provider with (any library ethersjs/viem) Here's an issue on this topic where it's explained bettter Would it be possible to add the chain id to the contract instantiation an maybe if there's not WC v2 provider throw an error when user is not in said chain (for writing calls) otherwise switch the WC provider to the said chain id? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
|
viem strictly follows EIP standards, which is single chain by nature. wagmi on the other hand, is multi-chain first, and has first class support for WalletConnect v2. I'd suggest to use |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
This question is better asked in the wagmi discussions area |
Beta Was this translation helpful? Give feedback.
viem strictly follows EIP standards, which is single chain by nature.
wagmi on the other hand, is multi-chain first, and has first class support for WalletConnect v2. I'd suggest to use
wagmi(React) or@wagmi/core(Vanilla TS/JS) if you would like multi-chain abstraction.