ZeqRelay — Zeqond-Stamped Relay

Zeqond-grid transport, mesh, routing, DNS.

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

What it does

Message relay with Zeqond timestamps and ZeqProof integrity. Every relayed message carries proof of its origin time and path — tampering detectable by any node.

Signature

Request

POST /api/network/relay

Param	Type	Required	Default	Description
payload	string	✓	—	Message payload (max 64KB).
destination	string	✓	—	Destination node or ZID.
ttlZeqonds	number		100	Time-to-live in Zeqonds (1–1000). Default: 100.

Response

{ relayId, zeqondStamp, proof, hops, estimatedDeliveryZeqonds }

Runnable example

curl -sS -X POST \
  -H "Authorization: Bearer $ZEQ_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "payload": "<value>",
  "destination": "<value>",
  "ttlZeqonds": 100
}' \
  "https://api.zeq.dev/api/network/relay"

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/relay in a language SDK so builders can call it in three lines.
• Medium — publish a reference integration demonstrating ZeqRelay — Zeqond-Stamped Relay alongside a real workload, with pulse-aligned metrics.
• Far — propose ZeqRelay — Zeqond-Stamped Relay 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.