Skip to main content

The clock

Everything in the framework rides one clock. Machines tick on it, contracts schedule on it, proofs stamp it, the audit chain orders itself by it, and the economy meters against it. It is not a convenience — it's the shared reference that lets a proof made on one node be checked on another.

The clock has three fixed numbers:

HulyaPulse — 1.287 Hz

The base frequency, exactly 10⁹ ⁄ 777 000 777 Hz. Every modulation and stamp derives from it.

Zeqond — 0.777 s

The computational second. Time is counted in whole Zeqonds since the Unix epoch, floor(t_ns ⁄ 777 000 777).

α — 10⁻³

The KO42 modulation amplitude, bounded by construction so the clock stamp never perturbs a result by more than 0.1%.

Watch it tick​

The pulse is public — no key, live on every node:

curl -s https://zeqsdk.com/api/zeq/pulse
# → { "zeqond": 2296532592, "phase": 0.0478, "R_t": 1.000296, "pulseHz": 1.287…, … }

zeqond is the whole-tick counter; phase is where you are inside the current tick (∈ [0,1)); R_t is the KO42 carrier at this instant. The execution model shows exactly where these enter a compute — as a timestamp, never as part of the physics.

Explore​

The time base

How the tick is defined and bridged.

The modulation

What the clock does to a result, precisely.

  • KO42 — the gauge mode — the bounded modulation R(t) = S₀·[1 + α·sin(2π·f_H·t)] and what the ≤0.1% figure really is