Closed gabrielkuettel closed 1 year ago
Hey @gabrielkuettel, thanks! We appreciate your effort & time, but since it is a breaking change for existing users (active sessions will end up disconnecting), we decided not to proceed with this change. Anyways, we are working on WalletConnect V2 migration, and we will address this issue with that migration. 🙏
In @txnlab/use-wallet, we allow multiple providers to be connected at the same time.
However, with providers based on
WalletConnect
, this isn't possible because they all use the defaultwalletconnect
key in browser storage to store metadata. This causes conflicts when multipleWalletConnect
providers are connected (e.g., Pera, Defly, or a generic WalletConnect session).Passing in a unique
storageId
key to theWalletConnect
constructor resolves this conflict.