privy

1/ It's a BIG day

EIP-7702 means ALL @privy users can get the benefits of account abstraction, like gasless txs, session keys, and more!

Privy offers seamless 7702 support on day 1, via integrations with ZeroDev, Ithaca, Biconomy, Pimlico, and others! 

Guide 👇

May end up being the most significant upgrade for mainstream adoption since I started paying attention. 

- subscriptions 
- better recovery
- automated actions

All powered by verifiable onchain security now. Big deal.

wdyt a/b the non revokable issue? is this an overstatement: 

security: you lose guarantees. trust shifts from code to the key.

from my non-dev, non-technical perspective, this is what i see

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

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

at trust wallet via sequence. pimlico. poap. polygon. metamask. paxful. flipside crypto. dash. bridgewater. darpa. secdef. navy. dia. linktr.ee/alexanderchopan

Yeah I think I disagree. 

Obviously it means acccounting for the huge amount of power the EOA keeps but I think people thinking about an “override” key and securing it (eg w key splitting, MPC, etc) makes for a very good pattern of:
- here’s a simple account w all the smart contract power ups
- it’s compatible w everything an EOA is
- you have this break glass in case of emergency fallback that needs to be protected at all costs. 

But ultimately while there are tradeoffs, I don’t think it’s a non starter (mind you my full time job is protecting EOAs so I’d be pretty depressed if I thought this couldn’t be done — this just makes it easier by enabling better disintermediation).