7702 
- EOA key still needs to be stored
- passkey signing is blind and confusing since the system UIs can’t be changed and refer to signing in
- passkey sync has holes (x platform)
- session keys UX unclear: how are keys requested? what’s the trade off between exposing complexity to users around restrictions vs making it magic but users don’t know what they’re approving?

“EOA key still needs to be stored”

😂

man. it’s hard having critical views of 7702 bc it’s so favored. it’s a band aid. and we need more folks talking ab it and holding us accountable.

intersend.io | via sequence. pimlico. poap. polygon. metamask. paxful. flipside crypto. dash. bridgewater. darpa. secdef. navy. dia. linktr.ee/alexanderchopan

It doesn’t need to be “stored” though :)

i’m excited to see solutions. 

“forgetting they key” is also weird to me. 

i know there is no ideal and all avenues have tradeoffs. i just want us to be able to say, ya we aren’t solving root causes and are just designing around eoa limitations.

why is it weird? 

if it's a post-quantum concern, then the issue is orthogonal as majority of multisig & execution signers are not PQ safe right now.

there are also proposal addressing PK deactivation:

there are also proposal addressing PK deactivation: https://github.com/ethereum/EIPs/blob/d96625a4dcbbe2572fa006f062bd02b4582eefd5/EIPS/eip-7851.md

yeah, the idea is that EOA key will be deactivated. so signature verification for that EOA won't work on execution / onchain.

“Deactivate/Reactivate a Delegated EOA's Key”

ok cool can i do the same w the eoa key that delegated this? no