walletbeat

Consumer Crypto

All for making crypto apps easier to onboard to and all, but it’s important to remember that abstractions have costs. Any kind of vendor lock-in at the wallet / account level is a losing strategy in the long term.

https://x.com/0xmakesy/status/1909258082414133268

Wallet interoperability is what makes this very scenario not a nightmare for users. If interoperability is lost, then web3 just created a new form of lock-in.
/walletbeat will do its part to preserve wallet interop. 🫡

Contributor @ /walletbeat.

Censorship resistance requires privacy.

Building /streme. Wanna be the very best. ゼニゼニ

Reading back on this thread, it sounds like I am blaming wallet users here. To be clear, I am not implying they are wrong or doing anything bad; I just mean that their collective action is what drives and what has driven the ecosystem. Responsible, but not guilty.

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.

What are the forces working against wallet interoperability?