A place for talking about the Ethereum Virtual Machine on Farcaster.

How Login in with Farcaster works

- Farcaster relies on a root ECDSA <> FID mapping onchain; this can be stored in any Ethereum wallet

- You use the ECDSA pair to create EdDSA keypairs for each app; this FID <> EdDSA mapping also lives onchain

- Hubs natively understand this

What are the properties of EdDSA keys that make them useful here?

EdDSA keys are my goto for generic signing - here's the rationale from when we designed Farcaster v1.

Pragmatism (Security) at OP Labs.
Prev: ConsenSys & Coinbase.

Attribs: Friendly, curious, introverted, mid-witted.
Chans: /eth-security /maurelian /stoicism




Technowatermelon. Elder Millenial. Building Farcaster. 

nf.td/varun

And what’s the difference between the key and key bytes in the contract?

And this the “signer contract” right?

And this the “signer contract” right? https://github.com/farcasterxyz/contracts/blob/main/src/KeyRegistry.sol

Would also say a developer can host an EdDSA key in the cloud (like an OAuth token) without a license or worrying about losing user funds