Skip to main content

Entangled State Explorer

Transition history, next-window claim, and event submission for a machine's per-machine entangled state.

Auth signed-in session Precision ≤0.1%

Open it on any node: zeqstate.com · zeqond.com · zeqsdk.com · zeqapi.com · zeq.dev

Every node runs its own sovereign instance — same app, its own entangled state.

What it does​

The detailed view of a machine's entangled state — the hash-linked, tamper-evident transition log every state machine carries. Inspect any machine's transition history, claim the next sealed window, and submit an event, all phase-locked to the 1.287 Hz system clock.

Each machine owns its own entangled state. Every transition is hash-linked to the prior row, Zeqond-stamped, and — through the PoEZ seal spine — expensive to silently rewrite. Integrity comes from cryptography plus elapsed time: a third party re-derives any result bit-for-bit and re-verifies the seal offline, with no account and no secrets.

Use it​

  1. Open the explorer on any node above, signed in.
  2. Pick a machine — its transition history renders newest-first, each row linking to the full envelope.
  3. Submit an event or claim the next sealed window; the row lands on that machine's entangled state and is immediately visible in the public observatory.

Verify what you're looking at, offline:

curl -s "https://zeqstate.com/api/chain/seal?seals=50" > seal.json
curl -fsSO https://zeqstate.com/verify-zeq-chain.mjs
node verify-zeq-chain.mjs seal.json

Honest limits​

  • Reads are public-tier; writes (event submission, window claim) are member-gated to the machine.
  • The explorer shows the entangled state; the proof is the offline verification above — don't take a UI's word for integrity when you can check the math.

Reference​