You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
// TODO(gomes): This says installed, so we only display... installed. Static ones (MM, Rabby, XDEFI) will either be displayed as their own section (EVM wallets/others), or
// TODO(gomes): wat do with these? two options here
// 1. keep filtering out and add as explicit options in the list (not under installed)
// 2. don't filter out, but still explicitly handle those 3 as they are not pure EVM wallets / rdns providers
// - keplr is an EVM/Cosmos SDK wallet, but we only support the latter (and if we were to use it as rdns provider, we'd only support the former)
// - Phantom is Solana + BTC + ETH, and we support it all (we'd only support the ETH part if we were to handle it as rdns provider)
// - Coinbase *is* an EVM-only wallet, but has some magic-QR pairing flow we support explicitly in hdwallet
constfilteredProviders=useMemo(
()=>
mipdProviders.filter(
provider=>
provider.info.rdns!=='app.keplr'&&
provider.info.rdns!=='app.phantom'&&
provider.info.rdns!=='com.coinbase.wallet',
),
[mipdProviders],
)
References and additional details
See above
Acceptance Criteria
Affected wallets: Keplr, Coinbase, Phantom
Regardless of installation, first-class flow is used for those wallets, not MIPD flow (which will usually look the same, visually at least, except for Coinbase where a QR pairing option exists)
Installed wallets show up in "Installed"
Uninstalled wallets appear in "Others"
Keplr still functions the same as in develop/prod i.e Cosmos SDK only, not EVM (despite being detected as EVM mipd provider)
Need By Date
No response
Screenshots/Mockups
No response
Estimated effort
No response
The text was updated successfully, but these errors were encountered:
Overview
Add first class support for those mipd wallets that really aren't.
Those are currently guarded against in the new flow, since we should handle them as first-class, which we don't yet:
web/src/context/WalletProvider/NewWalletViews/sections/InstalledWalletsSection.tsx
Lines 62 to 89 in 7fa4b50
References and additional details
See above
Acceptance Criteria
Need By Date
No response
Screenshots/Mockups
No response
Estimated effort
No response
The text was updated successfully, but these errors were encountered: