Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.neynar.com/llms.txt

Use this file to discover all available pages before exploring further.

Farcaster embraces rough consensus and running code as its governance model. Changes happen when someone makes a proposal, gets buy-in and ships running code. Depending on the change, different groups need to be convinced:
  1. Protocol devs, who choose to merge changes into hubs and contracts.
  2. Hub runners, who choose to deploy those changes to their hubs.
  3. App devs, who choose the hubs they read from.
  4. Users, who choose the apps they want to use.
Consensus emerges from people accepting new code or rejecting it. Farcaster will not have a binding voting process, official roles or veto power for anyone. Having too much structure ossifies systems, encourages politicking and slows progress. Rough consensus biases to action, encourages diversity of viewpoints, and maximizes decentralization, which is essential for a long-lived protocol. Most changes happen through the FIP process.