rns-time serves GPS-traceable time to mesh nodes over an authenticated Reticulum Link -- an NTP-style four-timestamp exchange, so a client can compute clock offset and round-trip delay and step its own clock. Works over TCP, I2P, and LoRa. The server refuses to answer as healthy while its upstream clock is in holdover.

Requests and responses are umsgpack. The client sends its send-time (t1); the server stamps receive (t2) and reply (t3); the client stamps receive (t4) and computes offset/delay. Responses also carry stratum + root dispersion; unhealthy (high-stratum / holdover) answers are rejected.

python3 -m rns_time.client e210fb416af335bd68a9ed4b86919895

python3 -m rns_time.client e210fb416af335bd68a9ed4b86919895 --set # step local clock

Want an ordinary NTP client to use this GPS clock instead? Link your machine to

the time server over the mesh: a MeshTunnel egress fronts this same clock on plain

UDP 123, so an unmodified chrony / ntpd / Windows Time pointed at 127.0.0.1 syncs

over Reticulum -- no internet time path.

pip install rns

pip install git+https://github.com/wdunn001/meshtunnel

pip install git+https://github.com/wdunn001/meshtunnel-launcher

git clone https://github.com/wdunn001/meshtunnel-launcher

meshtunnel-launch meshtunnel-launcher/examples/quasarke-ntp.toml

Then set 127.0.0.1 as your time source (chrony: server 127.0.0.1 iburst). Add

--install to bring the tunnel up at every startup (Windows or Linux). Stop your

OS time daemon first if it already holds UDP 123.

meshtunnel https://github.com/wdunn001/meshtunnel

launcher https://github.com/wdunn001/meshtunnel-launcher

Source https://github.com/wdunn001/rns-time

Live clock https://ntp.quasarke.net