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

- 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

> User is able to revoke an app's permissions w/ an onchain transaction using their root ECDSA

Are clients expected to offer their own UI that allow users to do this? Is it easy to do this today?

Understood, and that’s my bad, it’s been a while since I visited the “advanced” settings in Warpcast. Didn’t realize this is where you can manage the connections to apps.

No because most apps won't be Farcaster wallets and won't have access to the ECDSA key.