ZeqSync — Packet Synchronization

Zeqond-grid transport, mesh, routing, DNS.

• Protocol ID — zeq-sync
• Category — Network
• Endpoint — POST /api/network/sync
• Auth — api-key
• Rate limit — 120/min
• Version — 1.0
• Precision — ≤0.1% (KO42-enforced)

What it does

Zeqond-grid packet synchronization. Every packet timestamped to the 0.777s grid — no clock drift, no NTP dependency. The replacement for network time protocols.

Signature

Request

POST /api/network/sync

Param	Type	Required	Default	Description
clientZeqond	number	✓	—	Client's current Zeqond count.
clientPhase	number	✓	—	Client's phase [0,1).

Response

{ serverZeqond, serverPhase, drift, correctionMs, synchronized, R_t }

Runnable example

curl -sS -X POST \
  -H "Authorization: Bearer $ZEQ_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "clientZeqond": 0,
  "clientPhase": 0
}' \
  "https://api.zeq.dev/api/network/sync"

Integrate

1. Mesh health probe — tick against this endpoint each Zeqond and alarm on missing edges.
2. Routing seed — inject the returned topology into a BGP/QUIC shim for pulse-aware routing.
3. DNS drift — detect stale propagation by comparing pulse-stamps across resolvers.

Seeds

• Near — wrap /api/network/sync in a language SDK so builders can call it in three lines.
• Medium — publish a reference integration demonstrating ZeqSync — Packet Synchronization alongside a real workload, with pulse-aligned metrics.
• Far — propose ZeqSync — Packet Synchronization as an open reference standard so other runtimes can implement it verbatim against the Zeq paper.

Papers

• Zeq paper — https://doi.org/10.5281/zenodo.18158152
• Framework paper — https://doi.org/10.5281/zenodo.15825138

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