Skip to main content

Verifier Mesh — /api/mesh

The mesh, made public. Five sovereign nodes run the framework today — zeqstate.com, zeqond.com, zeqsdk.com, zeqapi.com, zeq.dev — each with its own database, vault, node key, and admin roster. What binds them is not shared state but a shared physics fingerprint: nodes running the same registry_version provably compute the same physics.

Endpoints 2 Source shared/api-core/src/routes/mesh.ts Auth none (public observatory data — counts and clocks, no PII, no machine internals)

MethodPathDescription
GET/api/mesh/selfThis node's card: public origin, registry version, git SHA, machine count, latest chain Zeqond, earliest genesis.
GET/api/meshSelf + every configured verifier peer, with registry_match and mesh_coherent computed.

How peers are wired​

The peer roster is ZEQ_VERIFIER_PEERS (comma-separated origins), hydrated from ZSC — the same roster compute envelopes fan attestations out to via POST /api/attest. Peers are fetched server-side (no browser CORS), with a ≈3,217 mz timeout, fail-soft: a down peer renders as alive: false — a card, never an error. A ≈38.6-Zeqond in-memory cache keeps observer refresh loops from stampeding the mesh.

Response (GET /api/mesh, shape)​

{
  "ok": true,
  "zeqond_now": 2289340151,
  "self_origin": "https://zeqstate.com",
  "registry_version": "sha256:…",
  "mesh_coherent": true,
  "nodes": [
    {
      "origin": "https://zeqstate.com",
      "domain": "zeqstate.com",
      "alive": true,
      "you_are_here": true,
      "registry_version": "sha256:…",
      "registry_match": true,
      "machines": 19,
      "latest_zeqond": "2289340150",
      "genesis_zeqond": "2278000000",
      "git_sha": "a1b2c3d",
      "rtt_mz": 0
    },
    { "origin": "https://zeqond.com", "domain": "zeqond.com", "alive": true, "registry_match": true, "rtt_mz": 41 }
  ]
}

rtt_mz is the round-trip to the peer in millizeqonds (1 mz = 0.777 ms — the page's one anchor). mesh_coherent is the headline claim: every reachable node runs the same registry, hence the same physics.

Runnable example​

curl -s https://zeqstate.com/api/mesh | python3 -c '
import json,sys
m = json.load(sys.stdin)
print("coherent:", m["mesh_coherent"])
for n in m["nodes"]:
    print(f"{n[\"domain\"]:<14} alive={n[\"alive\"]} registry_match={n[\"registry_match\"]} machines={n[\"machines\"]}")'

Honest limits​

  • A peer being alive: false means it didn't answer within the timeout — it says nothing about the peer's integrity.
  • mesh_coherent only covers reachable peers; an unreachable node is excluded from the claim, not assumed coherent.
  • Sovereignty is per-node software independence (own DB, vault, keys, admin roster). It is not a geographic-distribution claim — check each node's hosting yourself if that matters to your threat model.

See also​