ZeqTransport — Congestion Control

Zeqond-grid transport, mesh, routing, DNS.

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

What it does

Congestion control using R(t) modulation instead of TCP window sizing. Send rate modulated by HulyaPulse — naturally oscillates to find optimal throughput without packet loss.

Signature

Request

POST /api/network/transport/state

Param	Type	Required	Default	Description
connectionId	string	✓	—	Transport connection ID.
currentRate	number	✓	—	Current send rate (bytes/sec).
packetLoss	number		—	Current packet loss ratio (0–1).

Response

{ recommendedRate, R_t_modulation, phase, backoffMs, congestionState }

Runnable example

curl -sS -X POST \
  -H "Authorization: Bearer $ZEQ_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "connectionId": "<value>",
  "currentRate": 0,
  "packetLoss": 0
}' \
  "https://api.zeq.dev/api/network/transport/state"

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/transport/state in a language SDK so builders can call it in three lines.
• Medium — publish a reference integration demonstrating ZeqTransport — Congestion Control alongside a real workload, with pulse-aligned metrics.
• Far — propose ZeqTransport — Congestion Control 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.