embeddedwallets

If you're launching a wallet, should it be an EOA or Smart Wallet (4337)? 

EOAs become upgradeable with 7702 later this year, so you get the benefits of 4337 wallets and can upgrade to better standards over time. 

So it comes down to: upgradeable smart wallets (EOA + 7702 + 4337*) or pure smart wallets (4337 only) ?

This is a search we see a lot of builders working through at @privy in terms of how to set up their wallet stack. 

@v breaks it down thoughtfully. Another factor to account for is whether your app will be cross chain.

Technowatermelon. Elder Millenial. Building Farcaster. 

nf.td/varun

The easiest way to bring all your users onchain, regardless of whether they already have wallets | Customer love at privy.io/love

Data privacy on the web. Keeper of the fabric @privy.

Fmr Protocol Labs consensus work. Before that YC S14 🇫🇷🌐🍊

Reposting this oldie but goodie 

https://privy.io/blog/new-crypto-stack

I sometimes feel we miss the point when we start the conversation from the “building a wallet” POV.
From the user perspective they care about the dAPP not the wallet, meaning we do not have to bring a dAPP into a wallet but ideally do the opposite.

Wandering the Web3 world one swap at a time.
Product @Matcha.xyz

This approach created the horrible mess of UX we have in mobile right now, where , given the architecture choices around security for EOA or 4337, we have this continuous wallet<>dAPP bounce 

I would love to see the shift in approach here (embedded wallets solve this at the expense of portability)