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
12 recasts
47 reactions
notdevin
@notdevin.eth
How does FID creation work now that it’s all mainnet?
1 reply
0 recast
0 reaction
Dan Romero
@dwr.eth
It's still gated right now, but you register a FID for free (just gas). You need to pay for a storage slot with the storage contract. It's done as a single transaction during sign up.
1 reply
0 recast
0 reaction
notdevin
@notdevin.eth
Will that get exposed to the hub APIs once it’s fully open?
1 reply
0 recast
0 reaction
Dan Romero
@dwr.eth
Not sure I understand. All the FIDs are live on OP Mainnet now. You also need to create a signer (an EdDSA key) to start posting messages to Hubs. Warpcast handles the creation of FID, storage and signer during sign up.
1 reply
0 recast
0 reaction
notdevin
@notdevin.eth
That last one, the creation part. I wasn’t sure if Warpcast was the only door or just the front door
1 reply
0 recast
0 reaction
Dan Romero
@dwr.eth
Just the front door. Other apps can create signers (assuming they get the user to sign the package with the ECDSA key, i.e. the Farcaster wallet)
1 reply
0 recast
0 reaction
notdevin
@notdevin.eth
I can enable the user to extend the network once the FID exists, but I can’t grow the network by enabling our user to create their FID name and then subsequently connect the app, correct?
0 reply
0 recast
0 reaction
