ZeqNetcode

Physics engine, procgen, netcode, AI, spatial audio.

• Protocol ID — zeq-netcode
• Category — Gaming
• Endpoint — POST /api/gaming/netcode
• Auth — api-key
• Rate limit — 60/min
• Version — 1.287.0
• Precision — ≤0.1% (KO42-enforced)

What it does

Deterministic lockstep netcode on Zeqond ticks. 777ms authoritative frames, client-side prediction with R(t) rollback correction. Zero desync guaranteed.

Signature

Request

POST /api/gaming/netcode

Param	Type	Required	Default	Description
sessionId	string	✓	—	Game session identifier.
playerInputs	array	✓	—	[{ playerId, frame, inputs }]
currentFrame	number	✓	—	Current Zeqond frame number.

Response

{ authoritativeState, rollbackFrames, desyncCheck, latency_ms, zeqond }

Runnable example

curl -sS -X POST \
  -H "Authorization: Bearer $ZEQ_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "sessionId": "<value>",
  "playerInputs": [],
  "currentFrame": 0
}' \
  "https://api.zeq.dev/api/gaming/netcode"

Integrate

1. Domain solver — compose with KO42 + two additional operators from the matching family for pulse-coherent results.
2. Digital twin — pipe sensor data into this protocol every Zeqond to keep the model phase-locked with the system.
3. Alert threshold — flag results whose error_pct exceeds 0.1% as out-of-spec events for the operations layer.

Seeds

• Near — wrap /api/gaming/netcode in a language SDK so builders can call it in three lines.
• Medium — publish a reference integration demonstrating ZeqNetcode alongside a real workload, with pulse-aligned metrics.
• Far — propose ZeqNetcode 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.