reticulum.site

← simple search

Here you can open a Reticulum site without installing Reticulum. This server tries to link you to the site using the 'interfaces' (ways into the mesh) it has. You can add a so-called connection hint below to help it link. A connection hint is the address of a remote Reticulum interface or peer that this server can connect to, which may provide a better path to the site.

Original terminal view · An existing server connection was the verified local interface · nururl:///31d4652922efb9aa4154eca55923d5aa/page/post.mu?nn.post=2026-09-27-reticulum-live-decode.txt · Use web view

Interactive web view

A separate view where pages like this can become interactive, with editable text boxes, page buttons, and automatically updating sections. Seats are limited; this view uses its own session cookie. Text you enter is sent only when an updating section refreshes or you activate a page button.

Open this site in interactive web mode

Reticulum Live Decode (ct125)                                                                       
2026-09-27                                                                                          
                                                                                                    
Reticulum networks on LoRa in the UK commonly use 869.525 MHz with 250 kHz wide signals at spreading
factor 10, and this monitor listens there with an RTL-SDR running OpenWebRX+. OpenWebRX+ has no     
Reticulum mode, so its LoRaWAN decoder is set to 250 kHz and simply hands over every raw frame it   
receives, over MQTT, to a collector on the monitor node. Reticulum shares its LoRa sync word with   
MeshCore, so the collector picks out its frames by frequency and spreading factor, removes the      
one-byte RNode header, joins packets that were split across two LoRa frames and merges relayed      
copies into one line. Announces are fully checked: the signature is verified and the address is     
recomputed from the public key, so the node and user names shown are genuine. Announced NomadNet    
nodes become links to their pages, and LXMF addresses open a message. Everything else is encrypted  
end to end and shows only its type, size and destination. It was tested with a Heltec V3 flashed as 
an RNode, sending announces, data, path and link requests at 10 dBm. The log is at                  
84f4f45da60e8d9ac41f34b2b095a980.                                                                   
                                                                                                    
Back to the front page                                                                              
                                                                                                    
────────────────────────────────────────────────────────────────────────────────────────────────────
Comments or questions? Send a message: lxmf@9845aed67ab981c008f6c387aa2e97b9

Site address (destination hash) or nururl i Connection hint (interface) or nururl (optional for opening a site)

Accepted connection data: A hostname, IPv4 address, or Yggdrasil IPv6 address uses TCP; an omitted port becomes 4242. I2P accepts a bare 52-character B32 label, …b32.i2p, or i2p://…b32.i2p. Tor accepts a v3 …onion address or tor://…onion, with an optional port. Tor connections use this server’s Tor client and are never sent to DNS. A complete nururl may be pasted into either box. Leave this box blank to use the server’s existing connections.

nururl preview, generated automatically from the data above i

Connections/interfaces supported: public TCP/IP, Yggdrasil, I2P, Tor, and automatically discovered Reticulum interfaces.

Selected sites
Reticulum source code