> There's no seed/recovery phrase.
We talking about the same thing? I'm talking about this 24-word recovery phrase that, far as I understand, allows you to control the Eth address (wallet) that owns your fid (on Optimism). I'm no Eth person so that might be shaky but that's what I'm referring to.
I'm saying that's how cRyPtO worked in 2015, but we're moving past that in 2025. :)
Modern account abstraction doesn't rely on seed phrases, just signers. Again, think webauthn/passkeys or zero knowledge proofs (eg. cryptographic proof that i have access to some email).
I'll have to read up! I can't quite get my head around there not being private keys at the core of the onion, be they derivable from seed phrases or whatever else. (Nostr by contrast is pretty easy to digest, I'll give it that.)
Thanks for all this stuff, good article to kick it off.
I know what you mean, it is strange coming from a more programming-constrained environment like bitcoin.
With arbitrary onchain programs, the process of "signing" a transaction doesn't have to be an elliptic curve signature, but it can be "any program with a function conditionally returning true".
Comments
Apps have signers which get added to the contracts here: https://docs.farcaster.xyz/learn/architecture/contracts
If a signer is compromised, then it can do whatever the app could do.
We talking about the same thing? I'm talking about this 24-word recovery phrase that, far as I understand, allows you to control the Eth address (wallet) that owns your fid (on Optimism). I'm no Eth person so that might be shaky but that's what I'm referring to.
Modern account abstraction doesn't rely on seed phrases, just signers. Again, think webauthn/passkeys or zero knowledge proofs (eg. cryptographic proof that i have access to some email).
Here's a demo: https://porto.sh/
Thanks for all this stuff, good article to kick it off.
With arbitrary onchain programs, the process of "signing" a transaction doesn't have to be an elliptic curve signature, but it can be "any program with a function conditionally returning true".