Tony D’Addeo
@deodad
rundown of the different Ethereum accounts that are part of your Farcaster experience note that most of this isn't directly applicable to end users (just like an end user doesn't think about OAuth credentials) why so many? in short, they serve different functions and have different permissions. combined they yield a self custodial, user friendly account that is safely portable across clients and captures your full onchain public persona - custody address: holds your FID, root key for your FC account - recovery address: can recovery your FID if you loose access to the custody account, by default a Farcaster (the app) controlled wallet so we can do social recoveries for users - auth address(es): additional address that can sign in as you, used so you can sign in multiple clients w/o needing to import your custody address, your Farcaster Wallet is automatically added as an Auth Address and used to do SIWF on web
3 replies
4 recasts
21 reactions
Tony D’Addeo
@deodad
- verified address(es) - addresses you've publicly associated with your FID, they don't have any permissions related to your Farcaster account, especially useful in a world of embedded wallets where the # of wallets users have is high, your Farcaster Wallet is automatically verified for you (you can revoke if you don't want this) - primary address: the verified address you've publicly marked as primary to indicate people should send you assets there, your Farcaster Wallet is automatically designated as your primary if you haven't designated one already, easy to change - connected address: when you're using a Farcaster Client and go to do an transaction this is the account that does the tx, for most of your this is your Farcaster Wallet but we support Coinbase Wallet and Rainbow as well, this wallet is not necessarily related to your Farcaster account, for instance you might be connected to a burner wallet
2 replies
0 recast
5 reactions
will
@w
re primary address default, it's probably too late to do this but people who using ENSes should've had their primary resolutions respected, I think (unforunate, imo, that a user with an ENS handle can have a different ENS resolution than fc primary, tho i get *why* it's possible/happens)
1 reply
0 recast
1 reaction
boscolo.eth
@boscolo.eth
Thx for writing this up. How do signers fit into all of this? Also, is this captured in any of the protocol docs? I'm going to take a stab at wrapping W3C DID logic around the FID, and trying to figure out what keys do what in Farcaster. (Specifically, I'm trying to figure out which ones should map to "verificationMethod")
1 reply
0 recast
1 reaction
