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
- User is able to revoke an app's permissions w/ an onchain transaction using their root ECDSA - the app can treat them more like an OAuth token — don't need a Bitlicense to host them on behalf of the user. - if the user changes the FID <> ECDSA mapping (rotate keys for security reasons), app signers are preserved
So are you spinning up one individual wallet per account, upon account creation? Or is there a single farcaster wallet that holds all FIDs?
How does FID creation work now that it’s all mainnet?
What Offchain workers are running the Hubs? Are Hubs currently a trusted offchain solution running on cloud servers or can anyone run their own Hub?
What are the properties of EdDSA keys that make them useful here?
It's also helpful for someone new to know each App would also need its own App FID to sign for EdDSA https://warpcast.notion.site/Signer-Request-API-Migration-Guide-Public-9e74827f9070442fb6f2a7ffe7226b3c
I’m imagining a world where we can use session keys for this…
