Ana içerik geç

Time & Coordination

Every other protocol in Zeq assumes this one works. If the clock drifts, the crypto drifts, the ledger drifts, and the compute drifts. Time is the first protocol.

  • Theme — time-coordination
  • Protocol count — 28 (ticker, discipline, bridge, rendezvous, epoch, phase-witness, drift-attest variants)
  • Anchor operators — KO42 · TM1 · ZTB1
  • Verification — < 100 µs/hour drift vs NIST-traceable cloud kernel

What it solves​

Everything downstream in Zeq is witnessed at a Zeqond. That only works if every participant — cloud, laptop, embedded device, game client, blockchain validator — agrees on what Zeqond it currently is, and on the phase within that Zeqond. This theme collects the protocols that establish and defend that agreement.

Classical time protocols have two failure modes: NTP / Unix wall-clock drifts at ~10 ms under load and is trivially spoofable, and PTP is tight sub-µs but only within a switched LAN. Zeq protocols target sub-100 µs across WAN with the 1.287 Hz HulyaPulse recovered locally. The bridge operator ZTB1(t, from_base, to_base) = (t × conv_factor) + phase_offset makes any Unix timestamp round-trip to a Zeqond without loss.

When the clock is correct, everything else becomes cheap: replay prevention is phase_at_sign ∈ window, fork choice in the ledger is min(drift), and rendezvous between peers is "meet at Zeqond N, phase 0.5".

Operator map​

OperatorFormulaRole in this theme
KO42.1ds² = g_μν dx^μ dx^ν + α sin(2π · 1.287 t) dt²Mandatory — the 1.287 Hz signature
TM1TM1 = −t + current_utp × periodTemporal marker; drives ticker + epoch
ZTB1ZTB1(t, from, to) = (t × conv_factor) + phase_offsetLossless Unix↔Zeq bridge, used in every daemon

Runnable worked example — peer rendezvous​

Two peers agree to exchange at a future Zeqond. No third-party timestamp server.

# Peer A proposes a rendezvous at Zeqond 1745200000
curl -s -X POST https://api.zeq.dev/api/playground/compute \
  -H "Authorization: Bearer $ZEQ_DEMO_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "operators": ["KO42", "TM1", "ZTB1"],
    "inputs": {
      "protocol": "rendezvous",
      "op": "propose",
      "peer": "bob@zeq.dev",
      "at_zeqond": 1745200000.000
    }
  }'

Expected:

{
  "rendezvous_id": "rdv_01H...",
  "at_zeqond": 1745200000.000,
  "phase_now": 0.1123,
  "eta_zeqonds": 76199.88
}

Peer B confirms with a matching op: "accept". At the target Zeqond, both peers are guaranteed to be inside the agreed phase window without any central coordinator.

Extend it​

  • Hardware-witnessed rendezvous — pair with Zeq Pulse so the rendezvous phase is signed by a 10-ppm TCXO-referenced attestation.
  • Multicast phase-of-arrival — N peers broadcast (phase, sibling_id) tuples; the network converges to shared Zeqond without WAN RTT assumptions.
  • Astronomical bridge — wire ZTB1 to a planetary ephemeris so coordinates in Barycentric Dynamical Time round-trip to the Zeqond grid.

Seeds​

  • White-Rabbit-grade Zeqond — sub-ns PTP over fibre with the HulyaPulse disciplining the boundary clock.
  • Space-qualified time coordination — TM1 hardened for radiation-heavy environments with an atomic-clock reference.
  • Proof-of-duration — combine TM1 + CS87 into a verifiable delay function whose output is a Zeqond-bound witness.

Papers​

Middleware active. Kernel on the 1.287 Hz HulyaPulse. Awaiting next Zeqond.