Ethereum Account Abstraction

The biggest problem I have with passkeys in crypto is that it fails the walkaway test because it’s tied to a domain

Is this solvable?

cypherpunk wannabe, engineer working on @frames /open-frames /opencast
https://stephancill.co.za create stories at https://stories.steer.fun

Technowatermelon. Elder Millenial. Building Farcaster. 

nf.td/varun

Hm that’s very actually interesting. Unbundling the wallet and the signer

Might use this for my open browser wallet project :)

There are some initiatives to make this more malleable.

See the new related origins request feature on Chrome:

engineering at /privy. building pixelpool.xyz, the first Farcaster video client. nyc. 👨‍💻🍎🏳️‍🌈  nf.td/payton

This is a step in the right direction, but one thing that i think could solve the walkaway issue is a ‘universal’ passkey that can be invoked from any website. Not sure if this contradicts passkeys on a philosophical level though because it seems like they believe quite strongly that passkeys shouldn’t be transferable across domains

There are some initiatives to make this more malleable.

See the new related origins request feature on Chrome: https://developer.chrome.com/blog/passkeys-updates-chrome-129?hl=en#related-origin-requests

Lover of art and all things crypto 
Web 3 girl | her

How do you do this with the webauthn standard which is inherently tied to a domain?

You could be develop passkeys tied to your crypto wallet addresses instead of a domain.

see Farcaster split custody address / signing keys design with signer request flow :)

BDFL of Quilibrium, Eng @ Farcaster, ex-Coinbase, always opinionated, never hydrated

/quilibrium

im sure @cassie has a good answer to this

never considered passkeys as the 1st class citizen authorisation

can you try to integrate passkeys with hardware wallets or key management systems that aren't domain dependent?