Farcaster is a social networking protocol: a shared set of identity and message rules that different apps can use to build social products. It is not one single feed or app. A person can have a Farcaster ID (FID), authorize signing keys, and use compatible clients to read or publish protocol messages. The protocol’s account registries are on Optimism, while social activity is stored and distributed off-chain through its data network.
Accounts, keys, and posts
An FID is a numeric account identifier recorded in Farcaster’s identity registry. The registry associates the FID with a custody address; authorized signer keys can publish messages for that account. A cast, follow, reaction, or profile update is a signed message. This design separates a persistent protocol identity from any one app’s username, interface, feed ranking, or moderation decisions.
That separation improves the possibility of using more than one client, but it does not guarantee that every app displays every message or offers the same features. A client can choose what appears in its feed and what its own terms allow. Users should distinguish access to an account on the protocol from access to a particular company’s app.
From Hubs to Snapchain
For years, Farcaster’s data layer relied on Hubs: servers that received, validated, and replicated signed messages. Farcaster is transitioning its storage layer to Snapchain, a peer-to-peer network designed to store protocol data. The official Snapchain repository still describes the system as being in its migration phase, so older descriptions that say all current data simply lives on independent Hubs are incomplete, and it would be premature to claim that the transition is finished.
In practice, the protocol identity layer and the data-storage layer do different jobs. On-chain registries establish identities and authorized keys; the data network carries and serves posts and social actions. Snapchain’s current node and validator design, migration state, and supported messages can change as the software develops.
Apps, Frames, and Mini Apps
Warpcast was the name of Farcaster’s best-known client for part of the project’s history; the client later used the Farcaster name. Other apps can connect to the same protocol, though they may differ in features and moderation. Frames made it possible to interact with a compact app embedded in a cast. The newer Frames v2 design was renamed Mini Apps, which can open inside a Farcaster-compatible client and perform actions through that client’s supported capabilities. Mini Apps are app features, not a separate blockchain or a guarantee that every client supports the same integrations.
Ownership and the October 2026 change
Farcaster’s protocol, public code, and flagship app should be discussed separately. Neynar announced that it acquired Farcaster from Merkle in January 2026. On October 15, Neynar co-founder Rish said Network School was acquiring the Farcaster app, protocol repositories, and related products. The Block reported that the flagship app would be presented as the Network State Protocol and introduce new participation rules. The public technical documentation still uses the Farcaster name. Because this transfer and app changes are recent, check current announcements for details that may have changed.
What “decentralized” does and does not mean
Farcaster was designed to let people and developers use a shared protocol through different clients instead of relying on one company for every part of the social network. That architecture does not make every layer equally decentralized. The identity contracts, message network, client software, data services, moderation, and app ownership each have their own control points. A protocol can remain technically usable by compatible clients while its flagship app adopts different rules or limits posting. “Sufficiently decentralized,” therefore, describes a design goal and a set of trade-offs, not a promise that no company can affect a user’s experience.
Social Media Sentiment
After the October 2026 ownership announcement, a developer-led r/ethereum AMA about a proposed Hypersnap alternative drew questions about client compatibility, visibility of posts, governance, and what the new app’s rules mean for existing users. Some participants showed interest in another implementation; others were unsure how the changes affect their accounts. The thread’s allegations and the project team’s claims are not independently verified here, and one self-selected discussion does not represent all Farcaster users. The Block’s report describes the announced app changes but says it did not independently verify user reports of bans.
Last updated: 2026-10
Related Terms
- Optimism — the network that hosts Farcaster’s identity and key registry contracts.
- Farcaster Frames — an earlier format for interactive content inside social posts.
- Web3 Social — the broader category of social products that use blockchain or crypto infrastructure.
See Also
- Are Layer 2 Networks Actually Decentralized? — compares decentralization goals with the operators and control points a network relies on.
- Why DAO Governance Votes Often Fall Short — and Why Protocols Still Use Them — explains the trade-offs involved when communities and protocol teams make decisions.
- Arweave, Filecoin, and the Promise of Permanent Blockchain Storage — How Do They Actually Compare? — compares off-chain storage approaches relevant to social messages and media.
Swap crypto with ChangeNOW — explore a crypto exchange option while learning how social protocols connect to crypto services.
Sources
- Farcaster Protocol specification — defines FIDs, custody addresses, authorized signing keys, and how protocol messages are validated.
- Official Snapchain repository — describes the data-storage network, node operation, and the current migration status.
- Farcaster’s Frames v2 proposal — documents the interactive app format and its later Mini Apps name.
- The Block’s October 2026 report — reports the Network School transfer, the Network State Protocol app branding, and the announced participation rules.