rns.quasarke.net

Public Reticulum backbone & transport node · Quasarke mesh

Backbone status

checking…

Known paths

…
destinations reachable through this node

Connected clients

…
live RNS links on the public interface

Interfaces

loading…

How to reach this station: internet and overlay

Clearnet (TCP)
rns.quasarke.net:4965
I2P (anonymized)
…
Yggdrasil (overlay)
200:c8ba:8616:b482:eea8:883b:ac92:d80b
Add any of these as a Reticulum TCPClientInterface / I2PInterface to peer with the Quasarke mesh. The station is also peered to public backbones across North America, Europe, Asia & Oceania, so you reach the wider Reticulum network through it.
Get the apps to connect →

Radio & off-grid capabilities

This is a full unified-comms station, not just an internet node. It bridges Reticulum across these RF modes too:
LoRa · 915 MHz
914.875 MHz · 125 kHz BW · SF 8 · CR 5
Match these to reach the station over LoRa with no internet at all.
HaLow · 802.11ah
This is a high-bandwidth sub-GHz local mesh link.
Local WiFi · Reticulum access point
On-site, join SSID quasarke-rns and enable AutoInterface in your app. You are then on the mesh, and no internet is required.
HF · long-haul digital
This carries long-range HF digital across continents. It is amateur, and on-air transmission is pending licensing.
Packet · AX.25 (VHF/UHF)
This carries VHF and UHF packet data over the amateur bands.
Meshtastic bridge
Meshtastic LoRa devices relay into the Reticulum mesh and back.
Bluetooth
Pair a phone directly for mesh with no WiFi and no internet. This is still rolling out.

rns-time: authenticated time service

GPS-traceable time for mesh nodes runs over an authenticated RNS Link. It uses an NTP-style four-timestamp exchange and works over TCP, I2P and LoRa. The server refuses to answer as healthy while in holdover.
Destination hash
e210fb416af335bd68a9ed4b86919895
App / aspect
rnstime / time
Also: raw NTP over Reticulum (meshtunnel)
Prefer a stock client? A meshtunnel egress fronts this same GPS-backed clock on plain UDP 123, so an unmodified chrony/ntpd pointed at 127.0.0.1 syncs over the mesh. No rns-time client is needed, and no internet time path is used.
egress 874db2e2afd043320b38de431c15c173 · service ntp · one-command demo: meshtunnel-launch quasarke-ntp.toml
Setup instructions · Source · Live clock

rns-geo: geolocation data service

Geocoding, routing and nearby-POI lookups run over an authenticated RNS Link, trimmed compact enough for LoRa. It is a normal maps backend whose controller answers on Reticulum. Map tiles are not served over the mesh because they are too heavy, so this is data only.
Destination hash
2b20a86bfaf43c75810372dd73a53d1c
App / aspect · request path
rnsgeo / query · q
Ops
rev reverse-geocode · fwd geocode · route · near snap-to-road · poi · dir turn-by-turn directions
NomadNet node
🌐 RNS-GEO · includes a 🧭 turn-by-turn directions page (type two places)
Source

rns-wiki: offline encyclopedia

Full-text search and article retrieval over an offline Kiwix/ZIM library (Wikipedia, medical and reference content) delivered over an authenticated RNS Link. Articles are returned as NomadNet micron with inter-article links rewritten so the encyclopedia is walkable entirely over the mesh. No internet is required on the reading end.
Service destination hash
d4d6be6286955a56acaa66d60dfc5431
App / aspect · request path
rnswiki / query · q
Ops
search · article (rendered micron, deeplinks) · books
NomadNet node
📚 RNS-WIKI · open in a NomadNet client to search & read
Source

rns-weather: forecasts over the mesh

Type a US place; the service geocodes it with the station's own map data and returns the US National Weather Service forecast over an authenticated RNS Link. No internet required on the asking end. Coverage is US locations only, because the forecasts come from the National Weather Service.
Service destination hash
ddb5b002fd28cb81c35400b2eada2122
App / aspect · request path
rnsweather / query · q
Ops
fc forecast (place or lat/lon) · geo geocode
NomadNet node
🌦 RNS-WEATHER · open in a NomadNet client to type a place
Source

Beacon: search the mesh

A FOSS search engine for Reticulum: a crawler walks the announce stream and indexes NomadNet pages, and full-text search is answered over an authenticated RNS Link. Ranking blends text relevance with a MeshData schema bonus (well-described pages rank higher) and node trust; results link straight to the page on its node.
Search destination hash
4d076fb91fc004353527fb47c284d661
App / aspect · request path
rnsbeacon / query · q
Ops
search {q, limit, type}
NomadNet node
🔦 BEACON · open in a NomadNet client to search
Source

rns-news · full-text news over the mesh

Full articles from a curated feed set of national investigative outlets (Bellingcat, OCCRP, ICIJ, Snopes, Integrity Index), statewide desks, and local city newsrooms across ~27 US regions are fetched, stripped to plain text and re-transmitted into a NomadNet node, so off-grid readers get national and regional news with no internet. Browse by city or by topic. Every story is MeshData-tagged, so Beacon indexes it and it turns up in mesh search, including regional queries like “colorado news”.
NomadNet node
fbe7813b26a8858d552b10cd577abdcf
📰 RNS-NEWS · open in a NomadNet client · headlines at :/page/index.mu
Source

rns-resolve · human-readable names on the mesh

Reticulum addresses are 16-byte hashes, and there is no registrar to hand out names instead. rns-resolve fills that gap the way the network itself works: names are evidence, not authority. Look up a name and get ranked candidates, each with its evidence. Records registered here by their owners come first, then names heard in announces. Ownership is proved by derivation: the resolver computes the target from your own identity, so you can only register names for destinations your key actually generates. Answers are never authoritative; your client pins the one you trust and never asks again, so a later change is a loud warning rather than a silent redirect. Records are signed by the registrant and replicate between independent resolvers, so no single one is the root.
Look up or register a name (NomadNet node)
3435a207cc2d43cd7ea979e78e89dc16
🧭 RNS-RESOLVE · lookup at :/page/index.mu · register at :/page/register.mu · docs at :/page/docs.mu
Resolver service (MeshAPI, app rnsresolve)
5f382b5d0f73a8e35adce587ef7f05f0
Ops resolve / register / whois. A second, independent resolver replicates with it: ca8751d6d24dcab3a7175264641954a5
Node operators: register as part of your node setup rather than by hand. Running python -m rns_resolve.nodereg reads your node's own identity and name, signs, and renews.
Source · Design discussion

rns-shop · commerce on the mesh

The first e-commerce tooling for Reticulum: self-hosted storefronts with catalog, carts, orders, entitlements, and digital delivery over encrypted Links. Buyer identity = RNS identity (no accounts). Listings carry MeshData product records, indexed by Beacon. LXMF order confirmations/receipts.
Browse the demo shop (NomadNet node)
7a3b649379c6cc71ac0e7a75b6f38d52
Pages at :/page/index.mu · docs at :/page/docs/index.mu
Shop service API (MeshAPI, app rnshop)
fc86f0cb73b42ddbdf560b2c5a7628c5
This one answers ops, not pages.
Source · Spec

rns-everquest · a whole MMO over the mesh

A full EverQuest (EQEmu, RoF2) server played entirely over Reticulum. Your RNS identity is your account. Register and manage it from the NomadNet node, and one lightweight launcher fetches the client and tunnels you in. The game's UDP rides a meshtunnel with synthetic per-player IPs, so bans key on your Reticulum destination hash, not a spoofable IP.
Portal (NomadNet node)
c4623d0626f7401343c019d811658c36
⚔ RNS-EVERQUEST · register at :/page/account.mu · launcher download at :/file/eqplay.exe

meshtunnel · tunnel any UDP service over the mesh

A generic UDP-over-Reticulum tunnel: reach a service that has no public IP and no forwarded port, over nothing but Reticulum. Any UDP protocol works, including a game server, DNS, telemetry and NTP. Its companion launcher runs your end from a small config profile and can hold the tunnel up at startup on Windows or Linux. Two live demos ship pre-configured against this mesh.
Live demos (meshtunnel-launcher)
meshtunnel-launch quasarke-ntp.toml
stock NTP client over the mesh · and quasarke-everquest.toml for the game
meshtunnel · meshtunnel-launcher

html2micron · convert the open web to NomadNet

A small, dependency-free Python library (and CLI) that turns ordinary HTML into NomadNet micron, the markup that mesh pages are written in. Point it at a web page and get something a NomadNet client can actually read over Reticulum: headings, lists, tables and emphasis kept, navigation chrome and dead links stripped, and every micron escaping gotcha handled for you. Extracted from rns-wiki so any mesh project can reuse it.
Source

Content nodes on the mesh

Full sites mirrored as browsable NomadNet nodes. Open the hash in a NomadNet client to read them over Reticulum, no internet required. Each is its own independent node (not sub-pages of one another).
The Mild Take (NomadNet node)
3336fa70bd7604ddacf2fd65ba960724
📰 THE MILD TAKE · analysis & news at :/page/index.mu
Codec / codecai.net (NomadNet node)
0cec917e3dd520a1155490bc139edccb
🛰 CODECAI · token-native AI transport docs at :/page/index.mu
Status refreshes every ~60s. Public Reticulum transport node · coarse QTH 36.0°N, 83.9°W.