Degen

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

Web3 checkout should be approve-based. Set a spend limit (e.g. $50 USDC) for an app like FartApp. For no-click checkout, it just works. For normal flows, enter wallet address + confirm in wallet—like 2FA. No wallet connect needed. Safer, simpler.

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

@privy curious—why can’t I use my crypto wallet like a credit card? just enter a CVC or quick code and done.

gm. Fulltime degen, building fun stuff onchain. 
Master of Disaster Frogworks, /ottodao bullfrog, ex @astaria

I think walletconnect was working on something to send a request to your wallet without going through the whole connection flow. Dunno what’s the status there though. Been thinking about hacking something with Waku too 👀

Wish it worked more like a Visa card—just enter a number and confirm in your wallet app if needed. Signature could be a separate, simpler flow too—like entering a short code instead of going through a full crypto signing process.

Still need some kind of signature to order the transaction! Could be an in-app private key though instead of your wallet