Why · 01
Transport agnostic
End-to-end encrypted between peers. Re-encrypted at every hop. Bluetooth, Ethernet, UDP, Tor, Serial — same protocol, same mesh.
FIPSFree Internetworking Peering System
A self-organizing encrypted mesh that works over anything you can send packets through.
Why · 02
Same apps, new plumbing.
If it works over IP today, it works over FIPS — your stack doesn't notice.
⬡fren.fips×
Hacker News
Mail
⬡Hello from fren.fips 👋
This page is served straight from a peer on the FIPS mesh.
No DNS provider. No certificate authority. No exit node.
View source →Why · 03
Self-organizing
No coordinator, no setup. The mesh elects its own root, merges with neighbours on contact, and reroutes around damage on its own.
Nodes appear on shared media, beacon, and form peer links with whoever hears them. No setup, no coordinator.
Why · 04
One keypair. Three identifiers.
One Nostr secp256k1 keypair, generated locally — no registration, no authority. npub for sessions, node_addr (a SHA-256 hash) for mesh routing. A third fd00::/8 IPv6 hangs off node_addr just so unmodified apps can dial it.
Learn & Discover
Pick a thread.
Get Involved
Here's the code. Here's how to run it.
Tell us what breaks.
Run It
Install from GitHub releases, grab a tarball, or build from source. OpenWRT packages available. Docker test meshes for quick experimentation without hardware.
View releases →Break It
Test it. Find bugs. Stress the protocol. Try to break the encryption, flood the mesh, disconnect nodes at the worst moment. We want to know what fails before it matters.
Open an issue →Read the Specs
The design docs cover everything: protocol layers, packet formats, cryptography, routing algorithms. Start with the architecture overview, then dive into specific layers. 10+ specification documents.
Browse docs →Talk About It
Discussion happens on Nostr. Follow the contributors and check the relevant threads.
Join the conversation →