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

Smart Wallet announced Sub Accounts at ETH Denver that allows you to create an embedded account that is tied to a parent account to prevent fragmentation while preserving the UX benefits of embedded accounts. 

We’re actively improving this and would love feedback (cc @montana):

Since launching Sub Accounts for Coinbase Smart Wallet at ETHDenver, we've been exploring ways to simplify the dev experience -- making it as easy as just adding a few lines to your app's config

Here's a quick vid on how to set this up in wagmi! https://t.co/Pf0rpjVn4y

Montana Wong

Smart Wallet announced Sub Accounts at ETH Denver that allows you to create an embedded account that is tied to a parent account to prevent fragmentation while preserving the UX benefits of embedded accounts. 

We’re actively improving this and would love feedback (cc @montana): https://x.com/montana_wong/status/1907455174416711913?s=46

leading DevRel @base | former founder building onchain since '17 | sharing insights from the onchain frontier