Closed GMSteuart closed 1 year ago
@0xdef1cafe will need product review for user flow when clicking WalletConnect option
@GMSteuart I suppose this needs linking with https://github.com/shapeshift/hdwallet/pull/529 for now, could you add some instructions for local testing until hdwallet-walletconnect
is published?
Also, seems like the diff touches many files/lines that shouldn't be modified by this PR, rebase/merge might help 👀
@GMSteuart I suppose this needs linking with shapeshift/hdwallet#529 for now, could you add some instructions for local testing until
hdwallet-walletconnect
is published?
Ya, I can add local testing steps, one of those will have to be running the associated hdwallet-walletconnect package that isn't published yet.
Also, seems like the diff touches many files/lines that shouldn't be modified by this PR, rebase/merge might help 👀
Oh fun. lol. Glad I'm finding out earlier in the day rather than later. Thanks for pointing that out. 🙂
@GMSteuart I suppose this needs linking with shapeshift/hdwallet#529 for now, could you add some instructions for local testing until
hdwallet-walletconnect
is published?Ya, I can add local testing steps, one of those will have to be running the associated hdwallet-walletconnect package that isn't published yet.
Built, linked, and ran web off the hdwallet PR branch but I'm seeing this, so I'm wondering whether or not there are more steps or something I missed:
bumping this, any updates here @GMSteuart ser?
i connected a wallet with eth, btc, and atom assets
i can see tx history for eth and atom but not bitcoin
i can only see account data for eth
i'm only seeing eth account specifiers in the client
plz fix
@0xdef1cafe no longer a fuzzy fox 🙂
i connected a wallet with eth, btc, and atom assets i can see tx history for eth and atom but not bitcoin i can only see account data for eth i'm only seeing eth account specifiers in the client
I think this is an hdwallet issue. I'll make the necessary changes and publish a new alpha release, then include the updated dependency here.
edit: @0xdef1cafe Correction on this - WalletConnect 1.0 only supports ETH.
This is currently blocked by the hdwallet WalletConnect integration: https://github.com/shapeshift/hdwallet/pull/544
Keplr also supports WalletConnect, and can be used to connect to e.g osmosis.zone. It isn't supported at all as the app is effectively in full skeleton mode for dashboard and has no loaded accounts in state. Do we want to handle the case of Keplr Mobile (and Cosmos/Osmosis accounts derivation in WalletConnect) not being supported, by having some UX for it?
This is because WalletConnect 1.0 (the version we've implemented in HDWallet) is ETH-only. WalletConnect 2.0 has multi-chain support but is still in beta. I'm currently looking to see if it is possible to either detect the user wallet connected on the other side of the WalletConnect bridge or to limit the set of wallets supported by the application via WalletConnect.
SelectModal.tsx
merging as previously approved by @gomesalexandre and the most recent commit was stylistic/trivial
Description
Integrates WalletConnect wallet
UPDATE: Moved the provider object from hdwallet over to web since there is a scenario where the connect modal will hang indefinitely and there is no graceful way to automatically exit on behalf of the user. This indefinite situation occurs after the QR modal pops up and the user rejects the session. The reason this occurs is because the connector at the time is only listening for
connect
events and the only event emitted is thedisconnect
event; alas, the connector enters a state of waiting with no apparent end. The code of concern can be found in WalletConnect's web3-provider.Notice
Pull Request Type
Issue (if applicable)
Closes #1686
Risk
Testing
Open a terminal for web and another for hdwallet.
Screenshots (if applicable)
@0xdef1cafe copy on pairing modal will need to be updated since a QR code pops up:
On test.walletconnect.org
And lastly on test.walletconnect.org