Why · 01
Transport agnostic
End-to-end encrypted between peers. Re-encrypted at every hop. Bluetooth, Ethernet, UDP, Tor, Serial — same protocol, same mesh.
A self-organizing encrypted mesh that works over any medium that can transfer packets.
Why · 01
End-to-end encrypted between peers. Re-encrypted at every hop. Bluetooth, Ethernet, UDP, Tor, Serial — same protocol, same mesh.
Why · 02
If it works over IP today, it works over FIPS — your stack doesn't notice.
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
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 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.
Learn & Discover