-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Split out default wallet prefs for Ethereum and Solana #24079
Comments
cc: @darkdh |
Probable solution would be doing this #23898 rather than completely removing cc: @bbondy @jamesmudgett |
@mirkoschubert could you share what you have set for "Default cryptocurrency wallet" in brave://settings/wallet? |
@jamesmudgett Already did. 😄 I had But that's the issue: If you have set it to |
That's not the way defaults work ;) unless you mean we should break into more granular defaults like:
|
@jamesmudgett Btw, it did work with Solana support and But more granular defaults would fix the issue as well. 😊 |
"Default Ethereum/EVM wallet" |
@jamesmudgett — no edits from me. your copy makes sense. |
Verification passed on
Verification passed on
Verification passed on
|
Description
If you set the Brave wallet as the default cryptocurrency wallet in v1.41.96 and have another Solana wallet extension such as the Phantom wallet installed, you can't connect to dApps with the 3rd party wallet, even if you didn't create any Solana account in the Brave wallet.
Steps to Reproduce
Default Cryptocurrency Wallet
toBrave Wallet
at brave://settings/walletActual result:
After trying to connect to a dApp with a 3rd party Solana Wallet (e.g. Phantom Wallet) nothing happens and the connection failed. In the console of the Dev Tools there is an error message:
Expected result:
The dApp should easily connect to the 3rd party Solana wallet extension even with the Brave Wallet as default wallet, if no Solana wallet was created in the Brave wallet.
Reproduces how often:
Easily reproduced
Brave version (brave://version info)
Brave: 1.41.96 Chromium: 103.0.5060.114 (Official Build) (x86_64)
Revision: a1c2360c5b02a6d4d6ab33796ad8a268a6128226-refs/branch-heads/5060@{#1124}
OS: macOS Version 12.4 (Build 21F79)
Version/Channel Information:
I didn't have any problems before the 1.41.96 release.
Other Additional Information:
The issue is only applicable if a Brave wallet is present. I couldn't reproduce the issue with the Phantom extension in a private window, where the Brave wallet isn't enabled. On other browsers such as Chrome the issue doesn't appear.
Explanation:
It seems that the Solana part of the Brave wallet interferes with 3rd party Solana wallet extensions. Even if no Solana wallet has been created within the Brave wallet the
window.solana
object will be written before any other Solana wallets.There is a temporary solution: The user can always set the
Default cryptocurrency wallet
toBrave Wallet (Prefer extensions)
at brave://settings/wallet. This fixes it for now.But many users would update the Brave browser without knowing that something has changed and would get this issue instantly. They wouldn't think of changing this setting.
Possible Solution:
With the default wallet set to
Brave Wallet
, but no Solana wallet created, thewindow.solana
object shouldn't be written as well. So 3rd party Solana wallets would work as expected until the user creates or imports a Solana wallet within the Brave wallet.Maybe you should also warn the user if changes like that wouldn't work with current setting after an update.
The text was updated successfully, but these errors were encountered: