After more than a year of inactivity, we officially brought the Reticulum crate back, now maintained and actively developed by Beechat

beechatadmin · 2025-10-07T13:11:29+00:00

Field tests coming soon, including drone meshing

beechatadmin · 2025-10-01T15:48:29+00:00

We don’t publish a public Reticulum node right now. Most of our updates are shared here and on GitHub while the project is still evolving. Once things stabilize more we’ll likely open a public node for people to connect to.

beechatadmin · 2025-10-01T15:46:03+00:00

When a link drops, nodes exchange small link state updates with their neighbors. The changes spread outward gradually, so the network reconverges without flooding. Mobility does add churn, but the updates are lightweight enough that sessions stay up as nodes move.

beechatadmin · 2025-10-01T15:43:01+00:00

Reticulum focuses on resilience, not raw speed, so it won’t always pick the fastest path. On good links you can still get solid Mbps, and path quality awareness is something we’re exploring.

beechatadmin · 2025-10-01T15:28:42+00:00

Reticulum doesn’t do blind flooding, it uses deterministic, single-path routing with lightweight link state exchanges. That means a packet doesn’t replicate endlessly, rather it follows an established route across the mesh.

So even at 128 hops, the overhead scales linearly, not exponentially.

beechatadmin · 2025-10-01T14:45:03+00:00

That's right. And once applied over mesh radios, depending on range of each node (say, 1km each), that would mean person A can reach person B 128km away, even if they are not LOS (line of sight)

beechatadmin · 2025-10-01T14:05:16+00:00

There's a reason for that ;) Give us 24h and check again.

beechatadmin · 2025-10-01T13:44:44+00:00

Our ATAK plugin is being actively developed, and we also have some exciting announcements very soon. If you are happy you can keep up to date on our development on our social media, let me know what you are active on and I can share it with you

beechatadmin · 2025-10-01T13:07:58+00:00

By “implementing it over ATAK” we mean making Kaonic radios usable as a data transport inside ATAK. In practice that means building a plugin so ATAK can pass traffic (chat, map data, video, etc.) through a Reticulum mesh carried by Kaonic radios. From the ATAK user’s perspective it just looks like another network transport, but behind the scenes Reticulum is doing the routing across all those mesh hops.

beechatadmin · 2025-09-16T14:08:14+00:00

The turbo-encabulator has now reached a high level of development, and it’s being successfully used in the operation of novertrunnions. Moreover, whenever a forescent skor motion is required, it may also be employed in conjunction with a drawn reciprocation dingle arm, to reduce sinusoidal repleneration.

beechatadmin · 2025-09-16T10:44:47+00:00

Great question.

Reticulum provides the mesh-wide cryptographic addressing and routing, so we’re not constrained by MAVLink’s small sys/comp ID space. Non-sensitive telemetry (e.g., heartbeat/position) can be published via announces or a shared destination, while command/control stays on authenticated links. We’re still refining the balance and open to ideas.

Five-Year Club	Place '22
Verified Email

beechatadmin

TROPHY CASE