Farcaster Protocol Reference: Account Control, Signers, Storage and Snapchain

Authors	Farcaster protocol and documentation contributors
Document	Specification and documentation reference; review 2026-10-08
Project	Farcaster
License	Document license not verified; MIT not assumed
Official Source	Farcaster Protocol Overview

Farcaster’s protocol separates account control from social applications and message distribution. This reference reviews the original protocol overview alongside official documentation on 8 October 2026. Historical Hub architecture is identified separately from current Snapchain documentation; this is not an unchanged 2022 paper attributed only to its founders.

Identity, Keys and Recovery

The documented Id, Key and Storage registries are deployed on OP Mainnet. An Ethereum-format wallet address controlling an account does not mean every cast is stored on Ethereum mainnet. The November 2023 specification requires a registered FID, a valid signing key and sufficient storage for an accepted message.

Accounts obtain a numeric FID through the Id Gateway. App keys allow applications to publish for the account, separately from account ownership. The Key Gateway adds keys; the Key Registry provides lookup and removal. A compromised app key remains a risk until its authority is removed.

FIDs can be transferred and recovered under the registry rules. A receiving address accepts the transfer with a signature and must not already own a FID. A plain transfer preserves the recovery address; receiving an account without changing that recovery authority can leave another party able to recover it. “Non-transferable FID” is an incorrect description of these interfaces.

A Username Is Not the Account

The numeric FID and its selected username are different. The documentation distinguishes off-chain fnames, which Farcaster can revoke, from wallet-owned onchain .eth names. Changing a name does not itself change the account’s followers. Control of identity does not make every naming service censorship-proof.

Historical Hubs and Current Snapchain

The original overview describes signed messages and CRDT conflict resolution across Hubs. It explicitly acknowledges eventual consistency, unverified timestamps and non-permanent data. Media is referenced by URLs rather than stored inside each social message.

Current docs point to Snapchain. Its paper introduces ordered blocks for social data, using an external blockchain for account creation and fee collection. This adds consensus dependencies while enabling simpler synchronization. Social transactions are specialized actions, not arbitrary general-purpose smart contracts; pruning remains part of the design.

The migration guide calls Snapchain a replacement for Hubble and warns that successful message submission is best-effort: the message can still fail to enter a block. Submission, inclusion and delivery to a particular client’s feed are different events.

Storage and Application Boundaries

Storage is rented and bounded. The message documentation describes removal of older messages when limits are exceeded and possible loss after storage expires. Do not treat older quoted fees or capacities as immutable current settings. Open account control does not guarantee indefinite preservation of every post.

Current developer docs call Frames v2 “Mini Apps.” The Mini App wallet guide separately requests transaction confirmation from the user. Authentication credentials must be verified by an application’s server; a social identity or signed-in session does not automatically authorize a transfer of funds. Clients, hosting, external media and recovery services remain separate dependencies.

Social Media Sentiment

Not assessed for this technical reference. No dated discussion sample was collected; old activity totals and feature-launch excitement are not current sentiment measurements.

Last updated: 2026-10

Related Terms

Optimism — the ecosystem hosting the documented registries.
Public Key — verification of authorized signatures.

Sources

Farcaster protocol and documentation contributors. Farcaster Protocol Overview. Reviewed 8 October 2026. Historical hybrid model, signed messages, CRDTs and tradeoffs.
Farcaster protocol and documentation contributors. Farcaster Specification, version 2023.11.15 — contracts section. Reviewed 8 October 2026. Versioned identity, key and storage validation requirements.
Farcaster protocol and documentation contributors. Farcaster Contracts. Reviewed 8 October 2026. OP Mainnet registry deployment and contract roles.
Farcaster protocol and documentation contributors. Accounts. Reviewed 8 October 2026. Ownership, app keys and recovery setup.
Farcaster protocol and documentation contributors. Id Registry Reference. Reviewed 8 October 2026. Transfer acceptance and recovery-address persistence.
Farcaster protocol and documentation contributors. Key Registry Reference. Reviewed 8 October 2026. Signer removal and gateway distinction.
Farcaster protocol and documentation contributors. Usernames. Reviewed 8 October 2026. Numeric identity versus revocable fname and wallet-owned .eth names.
Farcaster protocol and documentation contributors. Messages. Reviewed 8 October 2026. Storage rent, bounded retention and user-reported timestamps.
Farcaster protocol and documentation contributors. Snapchain Whitepaper. Reviewed 8 October 2026. Ordered social data, pruning and consensus tradeoffs.
Farcaster protocol and documentation contributors. Migrating to Snapchain from Hubble. Reviewed 8 October 2026. Replacement for Hubble; successful submission is not block inclusion.
Farcaster protocol and documentation contributors. Farcaster Documentation Home. Reviewed 8 October 2026. Current Snapchain and Mini Apps documentation entry points.
Farcaster protocol and documentation contributors. Mini Apps: Interacting with Ethereum Wallets. Reviewed 8 October 2026. Wallet provider and separate user transaction confirmation.
Farcaster protocol and documentation contributors. Mini Apps: Authenticating Users. Reviewed 8 October 2026. Server verification of authentication credentials.