Forcing wallet-adapter to only show Solflare option is failing

[nikitavoloboev]

Describe the bug

I have this code:

  const network = WalletAdapterNetwork.Mainnet
  const endpoint = useMemo(() => clusterApiUrl(network), [network])

  const wallets = useMemo(() => [new SolflareWalletAdapter()], [])

  return (
    <>
      <ConnectionProvider endpoint={endpoint}>
        <WalletProvider wallets={wallets} autoConnect>
          <WalletModalProvider>
            <Outlet />
          </WalletModalProvider>
        </WalletProvider>
      </ConnectionProvider>
    </>
  )

Note the const wallets = useMemo(() => [new SolflareWalletAdapter()], []) line.

With above code, I still see this:

So it does not respect showing only Solflare. Unless there is another way to enforce a wallet?

[mcintyre94]

This is because wallet-adapter detects all wallet-standard wallets, without an adapter. Phantom implements wallet-standard, so all apps using wallet-adapter (with or without their adapter) will display Phantom as an option if it is installed. There is no API to restrict the wallets that are displayed AFAIK. Solflare also implements wallet-standard, so you don't need to include their adapter either.

If you really want to only support Solflare for some reason (and have your app broken in eg Phantom's mobile dapp viewer), you could use the Solflare SDK directly instead of wallet-adapter. Or you could fork wallet-adapter and modify it to only offer connection to Solflare. I wouldn't recommend that though, if a user has another wallet but not Solflare then they're unlikely to be willing to change wallets in order to use your app.

[xinKyy]

I hope to increase restrictions on displaying APIs for specified wallets. Thank you!