Farcaster
Platform · this deep dive is built from the official pages of the platform itself and of the tools that support it.
Overview
Farcaster is a microblog built on top of a blockchain. Its own documentation defines it this way: "Farcaster is a sufficiently decentralized social network built on Ethereum" (the Learn section). The same page calls it "a public social network similar to X and Reddit", where users "own their accounts and relationships with other users and are free to move between different apps".
Posts here are called casts. The architecture has two layers: account registration, keys and storage payments live in smart contracts, while the messages themselves live off-chain. For a marketer this means something unfamiliar: an account is created by a transaction, and space for messages is rented for money.
Apps, according to the documentation, split into "wallet apps", which "let you sign up, add connected apps, publish and read messages", and "connected apps" — read and publish only. The official client is made by the Farcaster team: "there is a web and a mobile app, but signup is only available on mobile".
Who's here
Farcaster does not publish audience numbers in its open documentation: none of the docs.farcaster.xyz sections we opened contains account counts, active user counts or a country breakdown. The farcaster.xyz home page returns only a heading without running scripts, so we take nothing from there either. A record we collected earlier notes the interface language as en.
An indirect signal about who is here is the technical framing: registration requires a transaction on the Ethereum network, and the Pro subscription is paid in USDC on Base (Tier Registry). The audience is inevitably skewed towards people with a crypto wallet. That is an inference from the platform's requirements, not a measurement.
Getting started
Registration is not a form but a sequence of on-network actions. The accounts documentation describes it: "any Ethereum address can register a Farcaster account by making an onchain transaction", after which the address is assigned a "Farcaster ID, or fid" through the IdGateway contract. Next you need to get a name, rent storage and add a key — a process that involves "many signatures and onchain transactions". Keys are managed by the KeyRegistry contract: the user issues them to apps, and they "let apps write messages on their behalf". Distinguish the custody address (which owns the account) from the recovery address, which "can be used to recover the account".
The username (fname) must match the pattern /^[a-z0-9][a-z0-9-]{0,15}$/ — 1–16 characters, lowercase Latin letters, digits and hyphens (the protocol specification). There is no separate business account in the documentation.
What you can publish
Limits are set by the validation rules in the protocol specification: cast text "must be at most 1024 bytes and a valid UTF-8 string", mentions "between 0 and 10", parent_url "between 1 and 256 bytes". The profile is also capped in bytes: avatar up to 256 bytes, display name up to 32 bytes, bio up to 256 bytes.
Bytes are counted, not characters: Cyrillic letters and emoji use 2–4 bytes per character, so a Russian text fits at roughly half the length of an English one. The guide to writing casts warns that emoji "take up multiple bytes even though they render as a single character", and sets an attachment limit: "a cast can have up to 2 embeds, each up to 256 bytes long".
The second limit is not length but volume. The messages documentation explains: "a storage unit costs $7 today, lasts one year and lets each account store a certain number of messages of each type". One unit covers 5,000 casts, 2,500 reactions, 2,500 links (follows), 50 profile data records and 50 verifications.
How to grow
Topical spaces here are channels. According to the documentation, "anyone can create a channel by paying a fee in the Farcaster client and choosing a channel name" (under 16 characters, lowercase letters and digits). The channel owner sets "channel norms that everyone agrees to on joining", pins and hides posts, blocks members and invites co-hosts. For a brand this is a managed community, not just a hashtag.
The second growth channel is mini apps. According to the publishing guide, a mini app is published via a manifest at /.well-known/farcaster.json on your domain and bound to a Farcaster account with "a cryptographically signed message in the accountAssociation property".
No ad account and no built-in creator analytics are described in the documentation we opened.
Path to monetization
Here, unlike in most decentralized networks, payouts are documented — though not in the form of "thresholds and percentages".
For developers: the publishing guide says outright that "verified mini apps are automatically eligible for Warpcast Developer Rewards, which are paid out weekly based on usage and onchain transactions". For creators: the client API reference has a Rewards section with a history of weekly award winners. Payout amounts, selection criteria and recipient geography are not described in the open documentation, so we name no sums.
Costs, by contrast, are described precisely. The Farcaster Pro subscription is handled through the Tier Registry on Base Mainnet: the tier with identifier 1 is called "Farcaster Pro", is paid in USDC, and is priced at "328767 wei USDC" per day, with a 30-day minimum term. Since USDC has six decimal places, that is about $0.33 per day, or on the order of $120 a year.
Storage is the second cost item: $7 per unit per year (the messages documentation), rented via the rent() and batchRent() methods of the Storage Registry contract, and "rented units are valid for 1 year from registration".
Tools and automation
The API is official. According to the reference, the host is always https://api.farcaster.xyz, and authorization uses a self-signed token created by an app key for a specific fid and passed in the Authorization: Bearer <token> header. Methods are available for channels, moderation, user data and rewards; for invites and removals a limit of "100 calls per caller per channel per hour" is stated. There is a protocol layer too: the documentation home page describes "syncing the Farcaster network onto a local machine so you can query the data".
Scheduled posting is technically possible through a key issued to an app. We found no list of third-party schedulers with confirmed Farcaster support in official sources.
Limits and rules
Farcaster has no single community rules document: the protocol does not moderate. Moderation is distributed across channels and apps — channel hosts block members and hide posts, and the client provides ban and hide methods through the API. The question "what is allowed here" is settled at the level of a specific channel and app, not the network.
The second constraint is money: how many messages you can store depends on the storage units you have paid for. The third is feature status: channels, according to their own documentation, are experimental, and their metadata and subscriptions "are currently only stored in the Farcaster client and may change".
Who it's for
Farcaster makes sense for projects that already work with a crypto audience: wallets, DeFi, NFTs, developer tools. Mini apps offer a rare thing — documented recurring income for a developer from the platform itself.
It does not suit brands with no crypto context: signup via an on-chain transaction, and only on mobile, will cut off most of an audience. It also does not suit anyone who needs long texts (1024 bytes) or a predictable cost of presence: storage and the subscription are paid in cryptocurrency.
Verified data
The checked data this deep dive rests on.
About the platform
the documentation defines Farcaster as «a sufficiently decentralized social network built on Ethereum»
The documentation's own wording
source, checked 2026-07-28
apps split into wallet apps (signup, publishing, reading) and connected apps (publishing and reading)
Signup is available only in the mobile app
source, checked 2026-07-28
Getting started
an account is registered by an onchain transaction from any Ethereum address; the fid is assigned by the IdGateway contract
The process includes getting a name, renting storage and adding a key
source, checked 2026-07-28
Account and access
keys are managed by the KeyRegistry contract; a key lets an app write messages on the user's behalf
The custody address and the recovery address are distinguished
source, checked 2026-07-28
the username (fname) must match the pattern /^(a-z0-9)(a-z0-9-){0,15}$/ — 1–16 characters
The protocol specification in the official repository
source, checked 2026-07-28
Content
a channel is created for a fee in the client; the name is under 16 characters, lowercase letters and digits; the host sets the channel norms and moderates it
Channels are described as experimental and not fully supported by the protocol
source, checked 2026-07-28
How the money works here
verified mini apps are automatically eligible for Warpcast Developer Rewards, paid weekly based on usage and onchain transactions
The payout amount is not stated
source, checked 2026-07-28
the client API has a Rewards section with a history of weekly award winners for creators and developers
Payout amounts, selection criteria and geography are not described in the documentation
source, checked 2026-07-28
Paid subscriptions
the Farcaster Pro subscription (tier 1) is paid in USDC on Base Mainnet: 328767 wei USDC per day, minimum term 30 days
USDC has 6 decimal places: about 0.33 USD per day, on the order of 120 USD a year
source, checked 2026-07-28
Pricing
a storage unit costs $7 and lasts one year
The price in the contract is dynamic; $7 is the value from the learning section
source, checked 2026-07-28
renting is done with the rent() and batchRent() methods; rented units are valid for 1 year from registration
The Storage Registry contract
source, checked 2026-07-28
Limits and restrictions
cast text — at most 1024 bytes and a valid UTF-8 string
Bytes, not characters: Cyrillic uses 2 bytes per character
source, checked 2026-07-28
mentions in a cast — between 0 and 10; parent_url — between 1 and 256 bytes
Protocol specification
source, checked 2026-07-28
avatar — up to 256 bytes, display name — up to 32 bytes, bio — up to 256 bytes
Protocol specification
source, checked 2026-07-28
a cast can have up to 2 embeds, each up to 256 bytes long
Developer guide
source, checked 2026-07-28
a storage unit holds 5,000 casts, 2,500 reactions, 2,500 links, 50 profile data records and 50 verifications
The volume of messages depends on the number of units paid for
source, checked 2026-07-28
for channel invites and removals a limit of 100 calls per caller per channel per hour is stated
Client API reference
source, checked 2026-07-28
API access
the client API host is https://api.farcaster.xyz; authorization uses a self-signed app key token in the Authorization: Bearer header
Client API reference
source, checked 2026-07-28
Languages
the interface language of the home page: en
The language is taken from the markup attribute, the versions from hreflang
source, checked 2026-07-28
Catalogue section: all similar See also: catalogue index · region: USA and Canada · scheduler comparison · find by situation · platform restrictions