Developer

Everything with real technical depth lives here rather than scattered across the site. The groups below are ordered the way a question usually arrives: what is this, what are the rules, how do I build it, what is actually proved, and where is it going.

Looking for a specific word — "custody", "fountain code", "watermark"? Use Search in the menu; it returns sections rather than pages, so a hit lands on the paragraph.

Start here

New to this, or coming back to it. Each answers a different first question.

ConceptsEach metaphor on the landing page, and the thing it is actually made of.
GlossaryWords this project uses in a particular way, each pointing at where it lives in the code.
Kernel flowsA message moving — four scenarios, every arrow recorded from a real node call.
What works todayCounted from the tree — what is tested, what has never met an antenna, and what is not written yet.

The protocol

What binds an implementation. Read the reference for the rules and the rest for the parts that are easy to get wrong.

Technical referenceThe wire format, the application layer on top, and where the core runs.
BridgesEvery medium SPORE speaks, and which are verified on real hardware.
DirectThe low-latency peer-to-peer pipe, and how NAT traversal works.
State machinesThe ratchet, the mix and the hub, drawn from the transitions they actually take.
RebuildReimplementing SPORE from scratch, with worked byte examples.
Reference decodersDependency-free Tier-0 decoders and the cross-language test vectors.
Language bindingsPython, Go and JS wrappers generated from one C ABI.

Build and run it

Working on the code, or on a device.

Dev guideRepo map, build commands per area, and where to look for what.
The browser nodeBuilding and hacking on the single-file web node.
Android device testsThe device-matrix checklist for the Android app.

What is actually proved

Claims with evidence behind them, and the places where there is none yet. Start here if you are deciding whether to depend on any of this.

Security maturityWhat has actually been tested, per component — and the column that is empty for all of them.
SimulationsEvery scenario the simulator runs, what each is for, and the numbers from the last run.
Hardware verificationWhat's been run on real radios and real devices, not just CI.
Threat modelSix chapters of adversary, what stops them, and the residual risk where nothing fully does.
Reporting a vulnerabilityHow to report, and what happens next.

The project

Where it is going, how it is run, and what happens if it stops.

RoadmapThe engineering plan, milestone by milestone.
ReleasesWhat shipped, in order, with notes generated from the commits.
MissionThe project charter and the decision test every change is held to.
ContributingFreeze rules, CI, branches, releases.
ContinuityWhat survives if you lose a device, this codebase, or this website.