name: '馃殌 Feature Request'
about: 'Suggest an idea for this project'
title: 'feat: Implement EIP-6963 for Multi-Wallet Discovery'
labels: 'enhancement'
assignees: ''
Is your feature request related to a problem? Please describe.
Currently, when a user has multiple browser wallets installed (e.g., MetaMask, Rabby, Coinbase Wallet), the dApp can't reliably detect all of them. This can lead to a frustrating user experience where the dApp might connect to the "wrong" wallet, or the user has to disable other wallets to connect the one they want. This is a common friction point for experienced Web3 users.
Describe the solution you'd like
I propose implementing EIP-6963: Multi-Injected Provider Discovery. This standard provides a unified way to discover all available wallet providers from a dApp.
By adopting this standard, the front-end could:
- Detect all installed and active wallets.
- Display a clear wallet selection UI, showing the icon and name for each discovered wallet.
- Allow the user to explicitly choose which wallet they want to connect to the dApp.
This would significantly improve the wallet connection experience, making it more robust and user-friendly.
Describe alternatives you've considered
The alternative is to maintain the status quo, which relies on a single window.ethereum object that can be overwritten by different wallet extensions. This is not ideal for users with multiple wallets.
Additional context
Implementing EIP-6963 would align DevDapp with the latest best practices for dApp development and demonstrate a commitment to a superior user experience. Libraries like ethers.js and wagmi are beginning to add support for this, making implementation more straightforward. This would be a great enhancement for "season-1" of the platform.
name: '馃殌 Feature Request'
about: 'Suggest an idea for this project'
title: 'feat: Implement EIP-6963 for Multi-Wallet Discovery'
labels: 'enhancement'
assignees: ''
Is your feature request related to a problem? Please describe.
Currently, when a user has multiple browser wallets installed (e.g., MetaMask, Rabby, Coinbase Wallet), the dApp can't reliably detect all of them. This can lead to a frustrating user experience where the dApp might connect to the "wrong" wallet, or the user has to disable other wallets to connect the one they want. This is a common friction point for experienced Web3 users.
Describe the solution you'd like
I propose implementing EIP-6963: Multi-Injected Provider Discovery. This standard provides a unified way to discover all available wallet providers from a dApp.
By adopting this standard, the front-end could:
This would significantly improve the wallet connection experience, making it more robust and user-friendly.
Describe alternatives you've considered
The alternative is to maintain the status quo, which relies on a single
window.ethereumobject that can be overwritten by different wallet extensions. This is not ideal for users with multiple wallets.Additional context
Implementing EIP-6963 would align DevDapp with the latest best practices for dApp development and demonstrate a commitment to a superior user experience. Libraries like
ethers.jsandwagmiare beginning to add support for this, making implementation more straightforward. This would be a great enhancement for "season-1" of the platform.