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

Feature Request: Support for Multiple Wallet Connections (Like Wagmi) #1050

Open
jexchains opened this issue Feb 10, 2025 · 1 comment
Open

Comments

@jexchains
Copy link

jexchains commented Feb 10, 2025

Currently, the Solana Wallet Adapter only allows a single wallet connection at a time. When a user connects a new wallet (e.g., switching from Phantom to Solflare), the previously connected wallet gets automatically disconnected.

Unlike Wagmi (Ethereum wallet adapter), which allows multiple simultaneous wallet connections, Solana’s Wallet Adapter does not retain previous wallet connections, making it impossible to manage multiple wallets at once.

Expected Behavior:

  • Allow multiple wallets to be connected simultaneously (e.g., Phantom + Solflare + Backpack).
  • Provide a way to switch between wallets without disconnecting previous ones.
  • Expose an API that tracks multiple connected wallets in state.

Why This Matters:

  • Many users hold assets across multiple wallets and want to interact with them within the same dApp.
  • Wagmi already supports this for Ethereum, making it easier for users to manage multiple accounts.
  • Would improve UX for Solana dApps where users need to use different wallets for different tokens or actions.

Possible Implementation Ideas:

  • Instead of overwriting the connected wallet, maintain an array of connected wallets in the adapter state.
  • Provide a switchWallet(walletName) API like Wagmi’s switchAccount().
  • Allow dApps to select a specific wallet for signing transactions without disconnecting the others.

Additional Context
If there are any roadmap plans for supporting this, we'd love to know!
Would appreciate any feedback from the team on feasibility and potential workarounds in the meantime.

Related Discussion: (If similar feature requests exist, link them here.)

@3girls1cup
Copy link

Forget it, look at this repo...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants