ZeqMesh — Node Discovery

Zeqond-grid transport, mesh, routing, DNS.

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

What it does

Decentralized mesh networking with lattice-coherence node discovery. Nodes announce themselves with ZeqPulse state — the mesh self-organizes by phase alignment.

Signature

Request

POST /api/network/mesh/discover

Param	Type	Required	Default	Description
nodeId	string	✓	—	This node's identifier.
capabilities	array		—	Protocol IDs this node supports.
radius	number		4	Discovery radius in hops (1–16). Default: 4.

Response

{ peers: [{ nodeId, phase, R_t, capabilities, latencyMs }], meshSize, avgCoherence }

Runnable example

curl -sS -X POST \
  -H "Authorization: Bearer $ZEQ_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "nodeId": "<value>",
  "capabilities": [],
  "radius": 4
}' \
  "https://api.zeq.dev/api/network/mesh/discover"

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/mesh/discover in a language SDK so builders can call it in three lines.
• Medium — publish a reference integration demonstrating ZeqMesh — Node Discovery alongside a real workload, with pulse-aligned metrics.
• Far — propose ZeqMesh — Node Discovery 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.