FIPS Project Update and v0.4.0 Release

It has been about six weeks since v0.3.0, and the response has been great. We estimate the public test mesh averages 1500-1600 nodes online at a time, with the optional bootstrap nodes peering with hundreds of inbound connections each.

FIPS

27. Juni 2026June 27, 2026 · 4 Min. Lesezeit4 min read

10

FIPS Project Update and v0.4.0 Release#

It has been about six weeks since v0.3.0, and the response has been great. We estimate the public test mesh averages 1500-1600 nodes online at a time, with the optional bootstrap nodes peering with hundreds of inbound connections each.

This growth is welcome on its own, but as planned its real value has been as a live test of the network design and implementation under real-world conditions that are far more demanding than any lab or CI test, including adversarial attacks and probing from the usual suspects. Running at this scale has surfaced latent bugs, race conditions, and capacity limits that have driven the bulk of the v0.4.0 release content.

In parallel, normal development work from existing and new contributors has continued, and this release has a few new capabilities that make it more than just a patch release.

Notable Contributions#


Community#

Beyond the code in this release, the wider FIPS community has been busy over the same six weeks.


Upgrade#

v0.4.0 is wire-compatible with v0.3.0. Linux, macOS, Windows, OpenWrt, and Arch (AUR) packages are on the release page, the Nix flake builds from source, and the public bootstrap nodes are ready for you to join.

Full release notes: release notes.

#fips#mesh

Written by

Comments10

ufm

There are a few questions: 1. Does anyone read the questions asked here? 3. Are they answered? 3. How is FIPS fundamentally different from Yggdrasil/Mycelium/cjdns? The answer “nothing, we just find it interesting” is perfectly fine :) 4. I set up two nodes. Both have at least one common public peer, test-de01. Both nodes can ping that peer. They cannot ping each other: "Destination unreachable: No route." Did I miss some setup step?
Open in a Nostr client

sandwich

3. Several differences. Uses nostr relays for discovery instead of a DHT, more resilient. Uses nostr pubkeys, inherits nostr identity features. Transport agnostic; Bluetooth, serial, LORA, Ham Radio, whatever, all on the table. 4. No idea.
Open in a Nostr client

pnk

1. Doesn't look like it and I also have a question 😅
Open in a Nostr client

sandwich

🤔 Image
Open in a Nostr client

pnk

Yes yes but I think the OP meant answers from the authors
Open in a Nostr client

ufmreplying to pnk

Yes, a reply from the authors would be interesting, especially on the third question. I’ve already figured out the fourth one myself. :)
Open in a Nostr client

sandwichreplying to ufm

... did you not see my response?
Open in a Nostr client

ufmreplying to sandwich

Neither Yggdrasil nor Mycelium uses a DHT. All of them use IP, and as a consequence, they also work over anything capable of carrying IP. P.S. What FIPS really does beautifully is fipstop. Unfortunately, it does not build on FreeBSD. And after Yggdrasil, its MTU size is just laughable.
Open in a Nostr client

pnkreplying to sandwich

No but at least I got the conversation going 👍
Open in a Nostr client

sandwichreplying to pnk

I am tagged as a contributor in the note you are responding to.
Open in a Nostr client

Contents

3 sections

  1. FIPS Project Update and v0.4.0 Release
  2. Community
  3. Upgrade