if you’re building a select your wallet interface is there any reason not to solely rely on EIP-6963 announced wallets for the options your present? vs using a hard coded list

Building @warpcast and @farcaster / dad / like to read, cook, ski, code

i suppose wallet connect doesn’t fit cleanly

what’s the strongest use case for wallet connect vs injected?

walletbeat

The push for embedded wallets as a promise for better onboarding UX.
The push for payment processor JavaScript libraries that favor some wallets over others.
And protocols like WalletConnect that act as intermediary in the wallet connection process, and sit in a position that can selectively block wallet connections.

None of these are problems on their own; they are actually useful and positive things. Where it gets pernicious is the over-reliance and over-acceptance of these solutions as a substitute for the real thing, and the fault for that lies mostly on wallet users.

WalletConnect works across devices, so you can connect mobile wallets. Similar UX as Sign in with Farcaster.

Of course that comes at the cost that WalletConnect becomes a centralized intermediary in the wallet connection process, and is thus in a position to censor.

Contributor @ /walletbeat.

Censorship resistance requires privacy.

another cost is UX, having built the x-device SIWF I can say users really dislike it

it's acceptable once in a while but if it's a daily thing vast majority simply won't do it

do you know if wallet connect offers a standalone extension so that users who really want this can opt into it?

WalletConnect works across devices, so you can connect mobile wallets. Similar UX as Sign in with Farcaster.

Of course that comes at the cost that WalletConnect becomes a centralized intermediary in the wallet connection process, and is thus in a position to censor.
https://warpcast.com/polymutex.eth/0xfb083717