Anyone can help build it.
Hypersnap is built by a global community of contributors — no company, no VC, no single owner. Code matters, and so do docs, design, ideas, and running a node. Here's where the work happens and how to plug in.
The public repositories.
Everything is on GitHub at github.com/farcasterorg. Every change is a PR. The snapshot below was last refreshed on May 20, 2026.
Rust
hypersnap
The open source, canonical implementation of Farcaster's Snapchain network. Snapchain is a data storage layer for the Farcaster social protocol. It is a blockchain like decentralized p2p network that stores data created by Farcaster users. Learn more about Snapchain's design from the whitepaper. The main goals of this implementation are: 1. High Throughput : Written in Rust and will process at least 10,000 transac...
- Stars
- 58
- Forks
- 22
- Issues
- 13
JavaScript
hypersnap-docs-web
Developer documentation for the Hypersnap Farcaster API, built as a static mdBook site with compile time search and LLM friendly plain text exports. src/ — plain markdown source, organized by topic ( concepts/ , reference/ , guides/ , agents/ , appendix/ ). book.toml — mdBook configuration. Compile time search is enabled — the index ships with the site, no external service required. theme/custom.css — minor visual...
- Stars
- 0
- Forks
- 0
- Issues
- 0
Repository
snap
Snaps are Snaps are simple, nimble apps embedded in Farcaster casts. This is the monorepo for the core packages, docs site, emulator, template, and examples. [!NOTE] This spec is in beta and may change rapidly in the near term. Tell your agent See docs.farcaster.xyz/snap for more info. Core library for Snap servers: schemas and types for snap JSON, validation of pages and POST bodies, and JFS verification for sign...
- Stars
- 1
- Forks
- 1
- Issues
- 1
Every kind of contribution counts.
You don't have to be a Rust engineer to make a difference. Here are some of the most useful places to start.
Write code
The protocol lives in farcasterorg/hypersnap: Rust node logic, hyper mode, storage, gossip, snapshots. Issues are open and triaged in public.
Improve the docs
Reference pages, guides, examples, LLM-friendly exports — anything that helps the next person figure something out faster.
Review what changed
The site auto-syncs from source and opens a PR when things change. A second pair of eyes on those PRs keeps the portal honest.
Run a node
The most direct way to make the network more decentralized. Every node added makes the whole thing harder to take down.
Improve node tooling
The operator helper lives at arcabotai/hypersnap: installer, doctor checks, sanitized reports, and safe repair workflows for people running nodes.
Tell people about it
Decentralized networks grow when people know they exist. Share the project, write about it, talk about it.
Bring ideas
Open an issue, start a discussion, sketch a design. The project moves on the strength of its contributors' thinking — yours included.
How the site stays honest.
A scheduled GitHub Action runs the same sync command maintainers can run locally, validates the site, and opens a reviewable PR whenever the source data changes.
Curated snapshots
The sync imports a focused set of facts: repo metadata, README summaries, release data, docs indexes, public node details, bootstrap commands, and architecture notes.
Daily, but only when there's news
The workflow ignores timestamp churn — it only opens a PR when the source repos actually have meaningful updates.