So I tried to step back and ask a simpler question: what is FIPS actually trying to do, and why should someone on Nostr care?
The short answer is that FIPS is trying to build a permissionless, encrypted, peer-to-peer networking layer. That sounds abstract, but the basic idea is simple: today, most of our digital lives still depend on centralized infrastructure. Even when we use Bitcoin or Nostr, we usually reach them through internet service providers, routers, DNS systems, cloud services, app stores, hosting companies, and other intermediaries.
The normal internet does not work like “my computer talks directly to your computer.” In practice, your device connects to your router, your router connects to your ISP, your ISP connects to other networks, and eventually your traffic reaches some server somewhere. On top of that, many devices are hidden behind home routers and firewalls, which makes direct peer-to-peer communication surprisingly difficult.
This is one of the problems FIPS is interested in. It asks whether networking itself can become more peer-to-peer, more resilient, and less dependent on central coordination. Instead of relying on a single VPN server, cloud provider, or fixed route, FIPS imagines devices forming an encrypted mesh. In that mesh, nodes can discover each other, connect through different transports, and help forward traffic across the network.
Physical infrastructure still matters. For long-distance communication, we still mostly depend on ISPs, submarine cables, datacenters, and telecom networks. What it tries to decentralize is the coordination layer: how nodes find each other, how routes are formed, and how trust is handled.
This is where Nostr becomes relevant. FIPS uses Nostr-style cryptographic identities, meaning a node can be identified by a public key rather than by a traditional account or centrally assigned name. Nostr can also help with discovery: not carrying the traffic itself, but helping nodes announce that they exist and share information about how they might be reached. For people already familiar with npubs and private keys, this part should feel philosophically familiar.
The exciting part is that FIPS is not limited to the normal internet. It is designed to work across different transports: UDP, TCP, Ethernet, Tor, Bluetooth, and potentially other mediums. That opens the door to interesting scenarios: local community networks, temporary networks at events, disaster recovery setups, censorship-resistant communication paths, or places where normal infrastructure is weak or unreliable.
There are performance and reliability tradeoffs. Centralized systems are often popular because they are efficient, easy to debug, and simple for users. Decentralized systems often gain resilience and sovereignty at the cost of complexity. That does not make them bad. It just means we should not pretend there is no cost.
FIPS is an alternative networking layer: something that can run on top of existing infrastructure, but can also take advantage of local or non-traditional connections when available. It is not a magic escape hatch from ISPs, but it may reduce how much power any single intermediary has over connectivity.
FIPS is exploring a problem that deserves attention. If we care about sovereignty, censorship resistance, and resilient communication, then we cannot only think about apps. Eventually, we have to think about the network itself.
And that is why FIPS is worth understanding. Not because it solves everything today, but because it forces us to look at a part of the stack we usually ignore.
quotingBrilliant podcast highlighting FIPS and the work the sovereign engineering is doing on Bitcoin and Nostr to bypass the legacy system and bring freedom tech to the world.
nevent1q…cefk
Thanks Gigi (npub1der…xzpc) and PABLOF7z (npub1l2v…ajft)
https://overcast.fm/+ABOqi78e4OU