Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[spike] Multi account for wallet connect #6691

Closed
0xean opened this issue Apr 15, 2024 · 5 comments
Closed

[spike] Multi account for wallet connect #6691

0xean opened this issue Apr 15, 2024 · 5 comments
Assignees
Labels

Comments

@0xean
Copy link
Contributor

0xean commented Apr 15, 2024

  • does wallet connect support multiple accounts
  • what is the lift to implement support for this
  • do this after all other multi account stuff is wrapped up
@0xean 0xean moved this from Backlog to Up next / groomed in ShapeShift Dashboard Apr 15, 2024
@woodenfurniture woodenfurniture self-assigned this May 22, 2024
@woodenfurniture woodenfurniture moved this from Up next / groomed to In progress in ShapeShift Dashboard May 22, 2024
@woodenfurniture
Copy link
Member

woodenfurniture commented May 22, 2024

@0xean or @twblack88 do you know of any wallets or dApps that support this? So far it appears to be theoretically possible but without anything to connect to it would be fairly moot.

On the plus side, we do currently support use of multiple accounts when connected as a wallet ✅

Image

When connected as a dApp we only see the first account ❌. This is something we should fix and would actually be useful. The example I see currently is ledger live connected to ShapeShift via WalletConnect, where 2 accounts are connected but we're only displaying the first one.

Image

@0xApotheosis
Copy link
Contributor

It's probably important here to confirm which side of the WalletConnect ecosystem we are talking about.

I believe this would be us, as a wallet, using WalletConnect to connect to other dApps.
It would be theoretically possibly to use our new account management UI to add new chains to the WalletConnect session via the session_update event.

As noted about @woodenfurniture, we are probably not handling the accounts a wallet gives us in the session payload when we are connected as a dApp, as we just use the existing logic to derive accounts, and so I assume if a wallet gives us an account with 0 balance in the session request we don't actually show it in ShapeShift without manually adding it.

@woodenfurniture
Copy link
Member

It would be theoretically possibly to use our new account management UI to add new chains to the WalletConnect session via the session_update event.

Agree, we absolutely should be emitting that event when accounts change, even if the dApp on the other end isn't handling this event

@woodenfurniture
Copy link
Member

Will turn this into tix

@woodenfurniture
Copy link
Member

Ticket for "Make ShapeShift as a WalletConnect dApp connect to all accounts in the request":
#7118

Ticket for "Make ShapeShift as a WalletConnect wallet/dApp emit/respond to session_update event when accounts change":
#7119

@github-project-automation github-project-automation bot moved this from In progress to Done in ShapeShift Dashboard Jun 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Done
Development

No branches or pull requests

3 participants