About This Server

As of today, there are only a handful of publicly reachable RoughTime servers. The protocol’s design explicitly depends on multiple, independently implemented servers for verification.

Independent implementations protect the ecosystem against more than just bad clocks. They also guard against software bugs, compiler differences, deployment errors, and latent assumptions in any single codebase. A client that can verify identical results across different servers — and also across different implementations — can trust that the result reflects real time, not a shared bug.

Our goal in writing a new implementation was to strengthen that independence. We wanted a modern, easily-audited Clojure implementation with clear interfaces, simple cryptographic primitives, and a transparent code path. By diversifying the ecosystem, we help make RoughTime more resilient.

Accurate, verifiable time underpins nearly every part of the web — from TLS certificates to log integrity, digital signatures, and distributed consensus. Traditional NTP and centralized time authorities cannot offer cryptographic proof of correctness; RoughTime does. It provides a lightweight, verifiable way to prove that an event happened after a known point in time, without requiring trust in the network path.

We believe RoughTime is one of the most important protocols of the modern web. It’s small, efficient, and conceptually elegant: each response forms part of a signed chain, making equivocation detectable and giving users a simple proof of time. We want to see it succeed and become widely adopted—and this server, and our Clojure implementation, are our small contribution toward that goal.