RMAP is a live map of the global Reticulum network - showing nodes, interfaces and gateways discovered automatically or registered manually by their operators.
Reticulum is a cryptography-based networking stack designed for resilient, decentralized communication. It works over virtually any medium - LoRa radio, TCP/IP, I2P, serial links, and more - with no central infrastructure required.
Every node on the network is identified by a unique cryptographic hash. Packets are routed hop-by-hop through transport nodes, and all traffic is end-to-end encrypted by default.
All communication is end-to-end encrypted. No exceptions.
Fully decentralized - no servers, no accounts, no registration required.
Works over LoRa, TCP/IP, I2P, serial, WiFi and more - simultaneously.
Transport nodes propagate paths and route traffic across the mesh automatically.
RMAP v4.7 is the current map, fully automatic thanks to the Reticulum interface discovery system. The earlier v3 (a manually maintained map) has been dismissed; the comparison below shows how the two differed.
| Feature | v3 Manual | v4 Auto-Discovery |
|---|---|---|
| Node registration | Manual form | Automatic |
| Node types | RNode, LXMF, NomadNet, TCP, I2P, Yggdrasil... | Any interface with discoverable = yes, plus NomadNet nodes, RRC hubs, propagation nodes, RetiBBS and PartyLine from their own announces |
| Data freshness | Updated manually | Live, updated on each announce |
| GPS coordinates | User-entered | From announce packet |
| Radio parameters | User-entered | Frequency, BW, SF, CR - automatic |
| Opt-in required | No (anyone can add any node) | Yes - only nodes with discovery enabled |
| Status | Dismissed | v4.7 online - rmap.world |
The search box on the map, and the one on the node list, look at every field a node publishes - name, hash, IP or I2P address, port, transport id, operator LXMF address, software and version, radio parameters, IFAC network, hops - including the fields the daemon decoded but cannot name yet.
Short names work as well: ip:, ver:, id:, sf:, bw:, freq:, net:.
The hop button on the map draws the links between nodes. Distances are measured from rmap: a node two hops away is two hops away from this server, not from you - from anywhere else the same node sits at a different distance. Links from rmap itself are off by default, because it is a backbone with a lot of direct peers; turning them on separates trunk peers (other nodes reach the network through them) from spoke peers (they relay for nobody).
The list is split in two groups. Network is every interface announced through RNS discovery: RNode, Backbone, I2P, KISS - and backbones reachable over Yggdrasil, Mycelium or Tor, recognised by their address. A backbone given as a hostname is looked up: if it points only to Yggdrasil or Mycelium addresses, it is shown as such; until the lookup has an answer, "ygg" or "Yggdrasil" in its name counts. Services are applications found from their own announces: NomadNet nodes, RRC hubs, LXMF propagation nodes, RetiBBS, PartyLine. A service has no position of its own: it appears on the map only at an interface run by the same operator.
Announces from applications rmap does not recognise are listed as Other, but hidden by default - many come from clients that misuse the protocol. Untick Hide unknown aspects to see them. Personal addresses (LXMF, phones) and remote shell, file and command endpoints are never listed.
The side list has two tabs, Nodes and Services, each with its own List filters (folded until you open them). Ctrl+click a filter to add it to the ones already picked; this works in the status bar and in the map filter menu too. Tick also on map and the map follows the list, both ways. The full list of types is on the RMAP Services page, under "What rmap finds"; totals, countries, RNS versions and more are on the Stats page.
An envelope next to a node means its operator published an LXMF address with discovery_lxmf_address, and the With LXMF Address filter leaves only those nodes. The announce counter carries the colour of the announce rate: green up to 3 announces/hour (one every 20 minutes), yellow up to 6/hour, and red above that - more often than one announce every 10 minutes, which no node needs to do. A red node also gets a thumbs down: flooding nodes are banned from RMAP and added to the blackhole, for a healthy network. Keep your announce_interval sane.
A new node is not judged at once: for the first 6 hours after its first announce its rate stays grey, "calculating" - a restart or a test can send a few announces in a row without being a flood. After that it gets its real colour.
A small amber arrow next to a node means it is running a version of RNS older than the current release; the tooltip says which one. It is a hint, not a complaint - but an up to date RNS is what keeps duplicate nodes off the map.
The node list shows every field of every node, twenty at a time, with the same search and the same filters as the map. Each card - and each popup on the map - has a Copy config button that writes the Reticulum interface section for you.
For a server node (Backbone, TCP, I2P) the snippet is the one you need to connect to it. For a radio node it is something else: the section is generic, because what you are copying is your own interface set up with the radio parameters needed to be heard by that node - same frequency, bandwidth, spreading factor and coding rate. No name and no identity of the other node travels with it, and TX power and serial port are left empty: those are yours to fill in.
For a Yggdrasil, Mycelium or Tor backbone the snippet notes that the overlay must be running on your system (RNS has no built-in Tor support: the connection has to be routed through Tor by your system). Services have no Copy config - they are not interfaces; a NomadNet node shows the address to open in NomadNet instead.
Reticulum includes a built-in interface discovery system. When you add discoverable = yes to an interface in your RNS configuration, your node periodically broadcasts a signed announce packet containing the full interface parameters - type, connection details, coordinates and radio settings.
These announces propagate through the network using the standard Reticulum announce mechanism on the aspect rnstransport.discovery.interface. RMAP v4 listens for these announces and automatically populates the map.
Only interfaces where you explicitly set discoverable = yes will appear on RMAP v4. Your node's existence on the network is never revealed without your consent.
Common questions about RMAP v4 and the Reticulum interface discovery system.
Check these requirements:
Location is set manually in the interface config using these parameters:
These fields work on any interface type - Backbone, TCP, RNode, I2P, etc. Without them the node appears in the side panel list but not as a map marker.
LoRa is a radio interface - it cannot directly reach the internet or RMAP's server. You need a transport node connected to both your LoRa interface and the internet via TCP. The transport node relays the discovery announce to the wider network. See the Quick Start guide for setup instructions.
Nodes are removed after 7 days without a new announce. As long as your Reticulum instance is running with discoverable = yes, it will re-announce periodically and stay on the map.
A LoRa RNode cannot reach RMAP directly - LoRa is a radio-only interface. Your discovery announces need to travel over TCP to reach the internet. This requires a transport node with both a LoRa interface and a TCP interface connected to the wider Reticulum network.
RMAP runs a public Reticulum transport node at rmap.world port 4242. Connecting your transport node here ensures your discovery announces reach RMAP at zero hops - the most reliable way to appear on the map.
The following discovery options are shown when set in the interface config:
Careful with ifac_netkey: it is the passphrase of your IFAC network. RMAP only reads announces that are not encrypted (the encrypted ones need a network identity we do not have and are discarded) - so if your node is on the map, that passphrase was in the clear and is now public. Everything a node announces is visible on the map and findable from the search box.
Interface discovery was introduced in recent versions of Reticulum: RNS 1.1.0 is the minimum. Use RNS 1.5.6 or later if you can - on older versions a node without transport enabled announces under a fresh identity at every restart, which is what fills the map with duplicates of the same node. The LXMF module must also be installed (pip install lxmf) as it is required by the discovery subsystem.
Not strictly required to publish your interface, but highly recommended. With enable_transport = yes, your node will also relay other nodes' announces, improving network coverage.
Discovery announces use the Reticulum destination aspect rnstransport.discovery.interface. RMAP v4 listens exclusively for this aspect, so only interfaces with discoverable = yes are collected - no other traffic is monitored.
Get your node on the RMAP v4 map in a few minutes. Choose your setup below.
If you run a Reticulum node reachable over the internet (VPS, home server with port forwarding), this is the simplest setup. Works on Linux and Android (BackboneInterface) or any platform (TCPServerInterface).
LXMF is required by the discovery subsystem.
Edit ~/.reticulum/config:
Add to the [interfaces] section. Use BackboneInterface on Linux (recommended) or TCPServerInterface on other platforms.
Add a client interface pointing to our server so your announces reach RMAP immediately:
Your node will appear on RMAP v4 within a few minutes. The default announce interval is 6 hours - set announce_interval = 60 to announce every hour instead.
LoRa is a radio-only interface - it cannot directly reach the internet. You need a transport node that bridges your LoRa interface to the TCP network. This can run on a Raspberry Pi, VPS, or any always-on Linux machine.
Discovery announces need to travel from your RNode over the air to a transport node, then over TCP to the internet and finally to RMAP. Without a TCP-connected transport node relaying them, your announces never reach us.
Radio parameters (frequency, bandwidth, SF, CR) are included automatically from the interface config. Location must be set manually.
Your RNode will appear on the map with frequency, bandwidth, spreading factor and coding rate filled in automatically. No manual registration needed.
If you don't have a public IP address or want anonymous connectivity, the I2P interface is a great option. You'll need i2pd running on your system.
On first start, Reticulum generates a persistent I2P b32 address for the interface. This address is what other peers use to connect, and is what RMAP displays in the node popup.
How to use and configure the interface discovery system from a client perspective.
reticulum.network/manual/using.htmlAll configuration options for making your interfaces discoverable, including all discovery parameters.
reticulum.network/manual/interfaces.htmlReach the RMAP admin on the Reticulum network:
Temporarily unavailable