Johnathan Corgan
5f033ef7e7
Conflicts resolved: - CHANGELOG.md: kept every [Unreleased] entry from master and added the twelve new maint entries under matching headings (Deprecated/Windows ahead of Removed; Fixed/OpenWrt, Fixed/Sessions and rekey, Fixed/Windows; a new Security/Sessions and rekey). maint's Fixed/Links and transports block is dropped: its two entries are already on master under Data plane and transports, in master's wording. - .github/workflows/ci.yml: both sides kept. The Linux unit-test job runs the flaky-test report right after nextest and then the privileged interface-binding step; the macOS job creates its address-less interface and then clears the cached nextest report; the Windows job takes maint's report cleanup. - testing/ci-local.sh: both the medium-change and mdns suites are listed, defined, dispatched and run. Adapted beyond the conflicts: the rekey resend test helper in src/proto/fmp/tests/core.rs no longer sets is_healthy, which master removed from the establish snapshot.
FIPS Documentation
FIPS (Free Internetworking Peering System) is a self-organizing encrypted mesh network built on Nostr identities, capable of operating over arbitrary transports — local networks, the public internet, Tor, Bluetooth, or point-to-point links — without central infrastructure.
With FIPS, your machine becomes a node in the mesh with a self-generated cryptographic identity. There are two ways to deploy it.
As an overlay on top of existing IP networks, FIPS lets your node reach any other FIPS node wherever it sits — behind a NAT, on a different ISP, on a phone over cellular, on a laptop with only Bluetooth in range, or behind a Tor onion. The mesh forwards IPv6 traffic transparently and end-to-end encrypted, with no central VPN concentrator or coordinating server.
From the ground up over raw Ethernet, WiFi, or Bluetooth, FIPS provides a complete permissionless network without any pre-existing IP infrastructure, ISP, or DNS. Any node that joins the link gets routable IPv6 addresses, peer discovery, and a path to every other node automatically.
Either way, existing networking software runs over it unchanged: SSH, HTTP servers, file transfer, anything IPv6-native works the same way it would on a local network.
New to FIPS? Start with the Getting Started guide.
Documentation Sections
Tutorials
If you are starting from scratch and want a guided path to a working mesh, go here.
How-To Guides
If you have a specific task in mind — enabling a feature, deploying a component, diagnosing a problem — go here.
Reference
If you need to look up wire formats, configuration keys, command flags, or counter inventories, go here.
Design
If you want to understand how the mesh self-organizes, why FIPS makes the choices it does, or how the pieces fit together, go here.
Releases
If you want the notes for a particular version — what changed, what broke, and what to do about it on upgrade — go here.