FrogTastic-RAM: Meshtastic, with the plumbing gone.
A Meshtastic node with its plumbing replaced by shared memory and nothing else changed. The client API stays exactly as it is, ToRadio and FromRadio over TCP, serial and Bluetooth, and so do Meshtastic’s modules and every existing app.
Existing Meshtastic applications are the acceptance test.
Kept, unchanged
The client API (ToRadio/FromRadio over TCP 4403, serial, BLE), Meshtastic’s modules and their semantics. The Python CLI and the incumbent’s suites judge it.
Replaced
Everything that moves packets between machines or repairs that movement, and every copy of another node’s data. A node writes its own truth into its own cells; other nodes read it with held reads.
Extended
The cells themselves, read and written from any machine on the memory through Ribbit’s own API. New applications see the whole mesh as state.
| check | result |
|---|---|
| Meshtastic’s own end-to-end mesh test, multicast blackholed | passes unmodified: zero UDP datagrams on the capture |
| the Python CLI | 40 of 40 |
| the distributed side-by-side, rehearsed on one machine: three nodes, a victim stopped for 20 s | every other node listed in 0.19 s; DM ACK in 0.50–0.61 s; victim gone and back within 0.6 s |
Two programs, two licences.
The firmware is Meshtastic’s (GPL-3.0); the Ribbit platform is FrogNet’s (GPL-2.0-only). They are not linked together: a separate FrogTastic-Bridge process carries the firmware’s calls to the memory over a local shared segment, and the segment keeps nothing. Without MESHTASTIC_RIBBIT the node is stock. Nodes that are not on the memory still get broadcasts and relays the stock way, over UDP or the radio.
This page replaces the earlier Meshtastic proposal; meshtastic.html now comes here.