rusty_time — chrony Remade In Rust For NTPv4 And NTS

Time is a security primitive wearing a clock face. Certificates, capability expiry, CRDT timestamps, "this login happened after that revoke" — if the clock is a lie, Trust is a lie. The daemon the serious Linux boxes reached for was chrony. The protocol is IETF RFC 5905 NTPv4. The implementation is C, and NTS is the authenticated path people keep meaning to turn on.

rusty_time is chrony remade: a pure-Rust NTPv4 and NTS client and server for Linux, macOS, Windows, and wasm. No C toolchain. NTPv4 in Rust is the point. The catalog is Remade with Rust. The thesis is rebuilding the foundation of the internet. This article is the clock.

Why rusty_time Is Chrony Remade For NTPv4 In Rust

A crafted NTP packet is a parser on UDP. Chrony is excellent C. It is still C. The NIST Secure Software Development Framework pushes memory-safe languages for network-facing daemons. rusty_time is that push. Chrony remade means the client and the server are Rust. NTPv4 in Rust means RFC 5905 without a C heap.

A crate that shells out to chronyd has not remade chrony. rusty_time is the remake. NTS is how the path authenticates. wasm is how a tab can still speak time without clang.

Trust, Security, and Incentive fail when the mesh node takes time from whoever answered port 123. Trust fails when expiry is a suggestion. Security fails when the daemon is C. Incentive fails when the safer clock is Linux-only. rusty_time is how those three primitives apply to a timestamp.

What rusty_time Ships As Chrony Remade

github.com/Remade-With-Rust/rusty_time is the source. Client and server. NTPv4 and NTS. Linux, macOS, Windows, wasm. That is the surface chrony won, minus the C. Chrony remade that only does a client on Linux is a toy. rusty_time does the job.

rusty_time Speaks RFC 5905 NTPv4

IETF RFC 5905 is the oracle. rusty_time is NTPv4 in Rust against that text. Interop is the product. Chrony remade that invents a sibling protocol is a science project. A mesh node has to take time from the same servers everyone else uses.

NTPv4 in Rust that cannot talk to a public pool is not a remake. rusty_time talks.

NTS On rusty_time — Time You Can Authenticate

NTS is Network Time Security. Unauthenticated NTP is "a stranger set your clock." rusty_time ships NTS on the client and the server so chrony remade includes the path people actually want in 2026. NTPv4 in Rust without NTS is half a product.

The Electronic Frontier Foundation has documented how "secure by default" claims collapse when the helper still trusts the open internet. rusty_time is how the clock claim becomes checkable.

Linux, macOS, Windows, wasm — No C Toolchain

A clock that only builds on Debian is a server product. rusty_time is a substrate product. Chrony remade for four targets, including wasm, is how a distributed cloud node and a browser tab share a protocol. No C toolchain is the house test — the same test as Rust on Arduino.

Deputy vaults the crate so the clock's supply chain is yours.

How rusty_time Feeds The Distributed Cloud

A mesh that cannot agree on time cannot agree on expiry. rusty_time is chrony remade so the mesh has a memory-safe clock.

Trust The Stamp, Secure The Daemon

Trust is a timestamp you can defend. Security is rusty_time — NTPv4 in Rust, NTS on, no C daemon. Incentive is chrony remade that runs on the four targets you already ship. The NIST Zero Trust Architecture tells operators to stop trusting the perimeter. rusty_time is how you stop trusting the UDP time oracle as well.

Capabilities expire. SpaceDB converges. Disco chunks seal. All of that assumes a clock. Chrony remade is how that assumption stays Rust.

Disco Party, Era 1, And Expiry

Disco Party is MATA's distributed cloud. Nodes need time to meter, to expire, to order events. Era 1 is the vault — a revoke that arrives "before" the grant is a clock bug. Era 3 is settlement. rusty_time is NTPv4 in Rust under both.

The Freedom Guide is personal data with TTLs. A TTL on a C chrony is a TTL on someone else's heap. The FTC cares about retention. Retention is a clock.

The Catalog Entry For rusty_time

Source is github.com/Remade-With-Rust/rusty_time. Cards and shipping status live on the Remade with Rust catalog. The mesh this clock feeds is what a distributed cloud is and the Disco Party. Digital Freedom is Trust, Security, and Incentive.

If you came from the Learn index looking for NTPv4 in Rust, this is rusty_time. If you came from chrony, this is the remake — client, server, NTS, no C. The internet you want to own still needs a clock. rusty_time is how that sentence stays true without the C.

The scheduler that needs a honest clock is Kairos. The language case is why Rust becomes the standard. Those clocks on the mesh, not in a region, are Rust edge nodes.