Skip to main content

Nodes and node-locality

The lattice is a fleet of nodes — zeq.dev, zeqsdk.com, zeqstate.com, zeqond.com, hulyas.org, and the rest — each running the same kernel. Two properties define it, and you can check both from your terminal.

1 — The surface is byte-identical​

Every node exposes the same API surface. Don't take that on trust — hash it:

for h in zeq.dev zeqsdk.com zeqstate.com; do
  curl -s "https://$h/api/endpoints" \
  | python3 -c "import sys,json,hashlib;d=json.load(sys.stdin);ps=sorted(e['method']+' '+e['path'] for e in d['endpoints']);print('$h', d['total'], hashlib.md5('|'.join(ps).encode()).hexdigest()[:12])"
done
# same total, same hash, on every node

Deploys keep it that way: one bundle is built, copied to every node's container, and md5-verified in place — a node that drifted would fail the check above.

2 — Machines are node-local​

Your machine is deterministic, not consensus-based. It lives on the node where it was spun up: its state, its chain, its clock are there, and a machine key presented to a different node answers for nothing. This is a design choice, not a limitation:

  • no consensus latency — your machine's clock ticks locally at the Zeqond rate, and a contract fire doesn't wait for a quorum;
  • a single, sealed history — one chain, one seal spine, no fork-choice ambiguity about what happened;
  • portability by envelope, not by replication — contracts export and tally coins migrate as verified envelopes; the history stays where it was made.

What is global is verifiability: a ZeqProof produced on one node can be checked on any other, because verification needs the envelope and the maths — not the machine.

The fleet fabric​

Nodes share a mesh (gossip channel), a naming layer (ZeqDNS .hz names), and cross-node attestation for the disputed verdict in precision & proof. Aggregators read every public machine through one SSE feed (GET /api/chain/aggregate/sse). The network APIs live in the reference; self-hosting your own node is the subject of the next pages in this section.

  • The machine — what exactly is node-local.
  • Proofs — why verification travels even though machines don't.