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

PREACH @nonlinear.eth !

Embedded wallets completely fracture identity and interoperability 

These embedded wallet providers have been in service of apps/platforms with little regard to the end user experience 

This needs to change

Stay Curious // iixii // Lazer Technologies // Prev: CoinDesk, Roc Nation // based

Normie users aren't coming for composability as the core value prop. That's an upsell over time.

Building /rodeo-club 🤠 and /foundation 🌐

"composability" no. "post once, publish everywhere" and "own your audience" maybe

The embedded wallet is exportable once they even understand they want this.

i think only a very small minority will even care to export. it's technically possible so that's good.

the core value prop is making money. embedded wallets don't get in the way of that. they get you there faster.

exportable to what? at this point, capital and identity have been atomized across 10s of apps. core web3 value prop in shambles

Such a valuable topic! Agreed on fragmentation being a burden mainly felt by users 

@getpara provisions universal wallets by default (since day 1)

Enter your email in 2 apps, get the same account

The user chooses whether to connect existing wallet or make a new one

Great then they have to remember every single app where they have a wallet

I like Para's approach which provisions universal wallets from the start

Great then they have to remember every single app where they have a wallet

I like Para's approach which provisions universal wallets from the start 

https://warpcast.com/nitya/0x68a6e676