good real-world example of how embedded wallets break identity

web3 becoming web2 but instead of email/passwords its now app-specific wallets (identities)

to fix, 1) devs must implement one-to-many identity mapping in thier app and, 2) users need to do the work of mapping (which they wont) *in every web3 app they use*

is this really a better ux than pasting a seed phrase in a pw manager? is this progress? 

given lack of web3 consumer growth the market says no

said that last year but no one seemed to listen...

@MacBudkowski Have you considered the in-app wallet route? https://t.co/88hlSPiVBb

@VitalikButerin Hey Vitalik,

Yes, we have considered in-app wallets. They work well on Farcaster, and we have our localStorage delegated keys for EIP712 signatures.

But…

1) Warpcast uses a wallet to bootstrap new identities for users (fid). It’s not what most apps want to do.

Most apps just

Mac Budkowski

said that last year but no one seemed to listen...

https://x.com/MacBudkowski/status/1863951819296153623

Building @kiwi 
Writing @ https://kanfa.macbudkowski.com/

Working on Farcaster and Warpcast. Longer thoughts at https://dwr.email

I think Farcaster solution makes a lot of sense. But I imagine it takes a lot of engineering resources to make everything work, which raises the bar for smaller projects. Alternative options are just painful vendor lock-ins.

Wallets were supposed to be a solution, but it's 2025 and Ethereum wallets are still terrible. No wonder why you decided to opt out of this crap.

It's only going to get worse. Every app will have a wallet.

So need a solution to tie them together (that's opt in).

Farcaster solves that today and will get easier as we add more functionality to mini apps for adding addresses.