Farcaster Sync Guide: Onchain Creator Monetization

Why sync matters for creators

Farcaster doesn’t run on a single server. Your casts, likes, and follows live across a network of independent hubs. This decentralization is what gives you control, but it also means your data isn’t automatically available everywhere. If you’re building a mini-app or checking analytics for monetization, missing data means missing revenue.

Think of hubs like post offices in different cities. Your message is posted to one, but it needs to travel to others to be seen by everyone. If a hub is offline or lagging, that message sits in transit. For a creator relying on onchain interactions to trigger payments or unlock features, a lagging hub looks like lost engagement.

This is why sync isn’t just a technical detail—it’s your income stream. Third-party tools query these hubs to verify your activity. If those hubs haven’t synchronized fully, your tool sees an empty ledger. You might have the followers, but if the hub hasn’t caught up, the mini-app can’t verify them. Ensuring your data is synced across the network is the first step to getting paid.

Choose a reliable hub provider

Farcaster is a sufficiently decentralized social network built on Ethereum, but your data doesn't move by magic. It lives in hubs—servers that store and sync your casts, profiles, and reactions. If you want your monetization tools to work, you need a hub that actually keeps up with the network.

The problem is that being "online" doesn't mean a hub is ready. A hub can be running but still lagging behind the rest of the network. You need to compare the sync percentage of a hub against the network to see if it's truly reliable. Querying hubs directly is the only way to verify this.

How to evaluate sync performance

Don't guess. Check the numbers. Look for hubs that maintain high sync percentages with the broader network. A low sync rate means your clients and apps might miss casts or show outdated data, which breaks the user experience you're trying to monetize.

When comparing options, focus on three things: sync speed, uptime, and API availability. A hub might be fast but crash often, or stable but have a broken API. You need all three to work together.

Hub comparison

Use this table to compare the major hub providers. Look for consistent sync rates and reliable API access.

Connect your client to the hub

Your monetization logic only works if your client can actually read and write data to the Farcaster network. This step is about linking your code to a Hub—the servers that store user data, messages, and casts. Without this connection, your mini-app is just a static page with no onchain identity.

Think of the Hub as the central ledger. Your client is the interface. If they aren't talking to each other, no transactions happen, and no revenue is generated.

1. Install the Farcaster SDK

Start by adding the official SDK to your project. This library handles the heavy lifting of signing messages and communicating with the Hub. It’s the bridge between your frontend and the decentralized network.

Run the following command in your terminal:

npm install @farcaster/hub-nodejs

If you are building a mini-app, you might also need the specific mini-app SDK for wallet integration and frame interactions. Check the Celo documentation for specific setup instructions if you are using Wagmi or other wallet connectors.

2. Choose a Hub Provider

You don’t need to run your own Hub node unless you are building a large-scale infrastructure. Most developers connect to third-party Hub providers like Neynar, Supercast, or Base’s official Hub.

For this guide, we’ll assume you are using a standard public Hub endpoint. If you are migrating to a standard web app on Base, ensure you are using the correct endpoint as outlined in the Base documentation. This ensures your app works seamlessly within the Base ecosystem.

3. Initialize the Hub Connection

Now, configure your SDK to point to the Hub. This is usually done in your environment configuration or a dedicated service file. You need to specify the Hub’s URL and port.

Here is a basic example of how to initialize the connection:

import { HubClient } from '@farcaster/hub-nodejs';

const hub = new HubClient('http://hub.example.com:2281');

Replace hub.example.com:2281 with the actual endpoint provided by your chosen Hub service. This connection is critical; if it fails, your app won’t be able to verify user identities or process payments.

4. Verify the Connection

Before you build out your monetization features, test the connection. Make a simple request to fetch a user’s profile or a recent cast. If the data comes back correctly, your client is talking to the Hub.

If you get a timeout or connection error, double-check your Hub URL and network settings. A broken connection here will break every subsequent step in your monetization flow.

Verify sync status and latency

Before you launch a monetization flow, you need to confirm your data is actually there. A hub being online doesn't mean it has fully synchronized with the network. If your sync percentage is low, your creator tools might miss critical events like payments or profile updates, leading to broken flows or lost revenue.

You can check your hub's health directly through the Farcaster SDK or by querying the hub endpoint. Look for the syncPercentage field. If it's below 95%, your hub is lagging. For real-time creator interactions, you want this number as close to 100% as possible.

Latency is the other half of the equation. Even if your sync percentage is high, a lag of more than a few seconds can disrupt live events. Monitor the lag metric in your hub logs. If you see consistent delays, consider switching to a more reputable hub or checking your network connection. Don't guess—verify. Your monetization depends on it.

Build mini-apps for monetization

Farcaster Sync works best as a sequence, not a scramble through settings. Do the minimum first: confirm compatibility, connect the core hardware, update only when needed, and test the result before adding optional features. That order keeps the task understandable and makes failures easier to isolate. After each step, pause long enough for the interface to finish syncing. Many setup problems are timing problems disguised as configuration problems. If the same step fails twice, record the exact error, restart the smallest affected piece, and retry before moving deeper.

The simplest way to use this section is to keep the setup small, verify each change, and record the stable configuration before adding optional accessories.

Frequently asked: what to check next

Here are the most common questions about syncing Farcaster hubs, building mini-apps, and setting up channels for creator monetization.

Work through The Farcaster Sync Infrastructure

1

Gather what you need

Confirm the materials, tools, account access, or setup pieces for The Farcaster Sync Infrastructure before changing anything.

2

Work in order

Complete one step at a time and verify the result before moving on. Most failed guides get confusing when two changes happen at once.

3

Check the finished result

Compare the outcome with the expected shape, connection, texture, or behavior, then adjust only the part that is actually off.

Previous

123

Next