Builder first: Rish on Neynar's new direction for Farcaster, live on Juke

A Friday audio Space on Juke, hosted by Nick (nickysap) with Zaal co-hosting, with Rish from Neynar shortly after the deal that put the main Farcaster client, the nodes, the APIs and Clanker under Neynar. Rish frames the shift plainly: the social-first experiment ran for four and a half years and did not work, so Neynar is running a builder-first experiment - primitives and in-client tooling so people can create new things on the internet without necessarily writing software. He is candid about the numbers (the Farcaster client sits at roughly 1,000 to 2,000 US daily actives, which cannot carry a team plus infrastructure costs, so growth matters but should decouple from the four-year crypto cycle), names three kinds of builder support (APIs, money through the Clanker ecosystem fund, distribution on Farcaster and X), and answers the decentralization question directly - Neynar holds protocol-level control because it pays the bills and runs on-call, and that can loosen if more teams can carry the protocol. On the Hypersnap fork: permissionless is fine, the name collision is not, and it forced a week or two of spam-prevention work. Nick notes he built Juke itself in about five days with Claude Code and the Neynar APIs - the thesis playing out live.

• Social-first ran four and a half years without sustainable growth; Neynar is now running a builder-first experiment for at least a period of time.
• Builder-first means primitives and in-client tooling, not expecting people to write software to create on the network.
• Three forms of builder support: developer APIs, money via the Clanker ecosystem fund (funded by Clanker revenue, not a huge fund), and distribution help on Farcaster and X.
• The Farcaster client is at roughly 1,000 to 2,000 US DAU - too small for the infrastructure it carries, so DAU growth is the number that matters, ideally decoupled from crypto cycles.
• Neynar keeps protocol-level control because it pays the bills and handles on-call; decentralization becomes realistic once multiple teams can carry the protocol.
• The Hypersnap fork is permissible, but the name collision created confusion and a heavy spam-prevention workload.
• The products that worked - Clanker, DEGEN, Bankr (as heard) - came from the community permissionlessly, which is the outcome Neynar wants more of.