File ecosystem.json contains the configurations of a growing list of Roughtime
servers. This file contains a brief description of how each server is
provisioned. Refer to README.md for information about adding your server to
the list.
The Chainpoint Roughtime service is hosted
at roughtime.chainpoint.org:2002. The public key, and information about
running the Docker container we've created for roughenough,
is provided at https://github.com/chainpoint/chainpoint-roughtime.
In addition to the Github repository README.md, the long-term public key in
Hexadecimal form is also provided as a DNS TXT record accessible with:
$ dig -t txt roughtime.chainpoint.org
The Chainpoint Roughtime service is in open beta, but aims to operate with
high-availability. The roughenough
Rust implementation of Roughtime is currently running on two servers in the
Google Compute Engine cloud (US-EAST4), both synced to Google's internal
high accuracy NTP service. These servers exist behind a public UDP
load-balancer and a Cloudflare DNS A record.
Cloudflare's Roughtime service aims for high availability and low latency. The announcement provides details about how we set up the service. Briefly, the domain for Roughtime resolves to an address in Cloudflare's anycast IP range (both IPv4 and IPv6 are supported), so the response may come from any one of their points of presence. The implementation is based on Google's Go code. This service is currently in beta. As such the root key is subject to change. It will be updated here and in the developer docs. You can also obtain it over DNS; see the docs for details.
This is Google's proof-of-concept server. It is experimental and does not, as of yet, provide uptime guarantees. The root public key is published here.
A public Roughtime server operated by the author of the Rust and Java implementations of Roughtime.
The server runs the latest release of roughenough
on a Google Compute Engine instance within us-central1 and sources time from Google's
leapsecond smeared NTP servers.
Available at roughtime.int08h.com:2002 its public key is stable and the service
is available 24/7.
The public key is available from the README.md in this project,
a blog post at int08h,
and the DNS TXT record of roughtime.int08h.com (see the
Chainpoint entry for how to look this up with dig).
Mixmin's Roughtime service resides on a dedicated Raspberry Pi running Arch Linux. The Pi has an Adafruit GPS module fitted and uses it to sync the system clock via NTP. It uses Adam Langley's reference implementation of Roughtime, written in Go and is compiled locally on the Raspberry Pi. The Roughtime server was announced on the mailing list, archived here. The announcement includes the server details.
time.0xt.ca runs on a stratum 2 NTP server hosted in Toronto, Canada.
The clock is synchronized with authenticated NTP connections to NIST (National Institute of Standards and Technology), and the Canadian equivalent, NRC (National Research Council Canada), which are both directly connected to atomic sources (caesium fountains and/or hydrogen masers). There are also multiple unauthenticated stratum 1 upstreams, maintained by GNSS (GPS + Galileo + GLONASS). The accuracy is typically within +/- 30 microseconds.
The Roughtime service is accessible at time.0xt.ca:2002. The public key is
available on time.0xt.ca's website, or through a DNS TXT
lookup.
dig TXT time.0xt.ca +short
The Roughtime service is powered by Google's Go reference implementation.
No uptime is guaranteed, but the server is constantly monitored for accuracy and availability. From time to time, there may be a few minutes of downtime for server maintenance.