FIPSFree Internetworking Peering System

A self-organizing encrypted mesh that works over any medium that can transfer packets.

Why · 01

Transport agnostic

End-to-end encrypted between peers. Re-encrypted at every hop. Bluetooth, Ethernet, UDP, Tor, Serial — same protocol, same mesh.

bluetoothethernetudptorserial

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
http://npub1qjk2nice…7pf2vpu.fips→ fd12:ab34::1
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.

ABCDEFGHIJPnodes power up, beacon on shared mediapeers found — packets start crossingmesh up — traffic flows

Nodes appear on shared media, beacon, and form peer links with whoever hears them. No setup, no coordinator.

Why · 04

One keypair. Zero registries.

One Nostr secp256k1 keypair, generated locally. npub for sessions, node_addr (a SHA-256 hash) for mesh routing. Existing applications see an ipv6_addr, no modification needed.

NOSTR · secp256k1your keypairsk · pkFSPsessionnpubnpub1qjk2nice…7pf2vpuapplication identity · who you talk toFMProutingnode_addr9a4f 7b21 c8e0 5f43… (16 B)routing identifier · what the mesh seesTUNlegacyipv6_addrfd9a:4f7b…for IPv6 appsroutes by node_addr · npub not known to mesh

Learn & Discover

Pick a thread.