Farcaster

• Name: Farcaster
• URL: https://www.farcaster.xyz/
• Category: social identity and publishing control plane / app-keyed social network infrastructure
• Tags: ethereum-ecosystem
• Summary: Farcaster is a split social stack: account custody, recovery, and storage rights stay explicit, while most publishing and graph propagation ride through hubs and app keys. That is the point. Farcaster is less a single social app than a portable identity-and-distribution layer with obvious operator choke points.
• What it does:
  • Uses onchain contracts on OP Mainnet to assign each account a unique Farcaster ID (fid) tied to an Ethereum custody address
  • Lets each account set a recovery address, creating an explicit account-recovery authority that can transfer the account if the owner loses access
  • Requires accounts to rent storage units, making write capacity a priced protocol resource rather than a free byproduct of account creation
  • Lets accounts register app keys so third-party apps can publish messages on their behalf without taking over account custody
  • Replicates account activity and social data through hubs and related sync tooling rather than storing the full social graph directly in one L1/L2 contract set
  • Offers Sign In with Farcaster so external apps can authenticate users with Farcaster identity and pull public profile and social-graph context into onboarding flows
• Key claims:
  • The official contracts docs make the architecture unusually clear: identity, app authorization, and storage are three separate policy surfaces managed by distinct registries.
  • The fid model matters because Farcaster accounts are not just usernames. The durable root object is a numbered account bound to Ethereum custody, with usernames and app UX layered above it.
  • Recovery addresses are analytically important because they introduce a formal social-recovery / admin surface into account ownership. The real control question is not only who holds the custody key today, but who can recover the account tomorrow.
  • Paid storage is also a real governance lever. Because accounts rent storage rather than writing for free, protocol admins and pricing policy shape who can publish cheaply, how spam resistance works, and how much durable state a user or app can sustain.
  • The Key Registry is the most reusable design insight for the broader corpus: Farcaster separates account ownership from app operation by letting accounts authorize publishing keys. That is closer to delegated capability infrastructure than to a monolithic wallet-login flow.
  • Sign In with Farcaster extends that logic outward. External apps can authenticate against a Farcaster identity and immediately use social data, which turns Farcaster from a social app into an identity-and-distribution layer for other apps.
  • Farcaster contrasts cleanly with the nearby social notes. EFP is a portable list registry; Lens pushes much more of the social object model and policy surface onchain; Farcaster keeps account authority legible but leaves most social activity to hub-replicated network state.
  • This entry belongs in the corpus because it clarifies where authority sits in a crypto-social stack: in custody addresses, recovery addresses, storage pricing, app-key issuance, hub operation, username assignment, and downstream app authentication.
• Whitepaper: No canonical standalone Farcaster whitepaper surfaced in this pass. The strongest primary materials were the official site, official docs on contracts and Sign In with Farcaster, and the official repositories for hubs, contracts, and auth tooling; see ../whitepapers/farcaster-primary-sources-2026-05-10.md.
• Sources:
  • https://www.farcaster.xyz/
  • https://docs.farcaster.xyz/
  • https://docs.farcaster.xyz/learn/architecture/contracts
  • https://docs.farcaster.xyz/reference/contracts
  • https://docs.farcaster.xyz/reference/contracts/reference/id-registry
  • https://docs.farcaster.xyz/developers/siwf
  • https://github.com/farcasterxyz
  • https://github.com/farcasterxyz/contracts
  • https://github.com/farcasterxyz/hub-monorepo
  • https://raw.githubusercontent.com/farcasterxyz/hub-monorepo/main/README.md
  • https://github.com/farcasterxyz/auth-monorepo
  • https://raw.githubusercontent.com/farcasterxyz/auth-monorepo/main/README.md

Internal linkages

• Keep this note on the few adjacent cuts that matter: lens-protocol, ethereum-follow-protocol, and eip-4361.
• Useful cut: Farcaster is a social control plane with explicit custody, recovery, storage, and app-key surfaces — not just another crypto-social app.

Control surface

• The leverage sits in custody and recovery addresses, storage pricing, app-key issuance, hub operation, username policy, and which clients users treat as canonical.

• Farcaster keeps some authority visible. It does not eliminate operator power; it just moves more of it into places you can name.

• Last reviewed: 2026-06-03 UTC