Content
@
0 reply
0 recast
2 reactions
Dan Romero
@dwr.eth
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
8 replies
13 recasts
47 reactions
Dan Romero
@dwr.eth
- 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
1 reply
0 recast
4 reactions
Ghostlinkz
@ghostlinkz.eth
> 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?
1 reply
0 recast
0 reaction
Dan Romero
@dwr.eth
No because most apps won't be Farcaster wallets and won't have access to the ECDSA key.
2 replies
0 recast
1 reaction
Ghostlinkz
@ghostlinkz.eth
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.
1 reply
0 recast
0 reaction
Liang @ degencast.wtf 🎩
@degencast.eth
Interesting! So when building a farcaster protocol client, you could build a farcaster wallet(manage the key) or just farcaster app(relying on warpcast) Does this mean it's impossible to just use metamask to manage your farcaster key/fid ?
0 reply
0 recast
0 reaction
