Skip to main content

Entangled State Explorer

Block history, next-block claim, event submission — for the per-machine entangled state. (Formerly listed as "Zeq Blockchain"; the app ID and URL keep that historical name.)

App ID zeq-blockchain Live ZEQ_BASE_URL/apps/zeq-blockchain/ Auth signed-in session Precision ≤0.1%

What it does​

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

The filename keeps the historical zeq-blockchain ID, but be precise about what this is: not a blockchain. No consensus, no mining, no validators, no global ledger. Each machine owns its own chain — every transition is hash-entangled with the prior row, Zeqond-stamped, and (via the PoEZ seal spine) expensive to silently rewrite. Integrity comes from cryptography plus elapsed time, not from a network vote.

If you build blockchains, the relevant offering is different: ZeqVM gives you deterministic recompute (anyone re-derives a result bit-for-bit), Zeqond-anchored temporal sealing, and offline verification — services you can anchor an external chain to, not a chain of ours competing with yours.

Use it​

  1. Open /apps/zeq-blockchain/ signed in.
  2. Pick a machine — its block history renders newest-first, each block linking to the full envelope.
  3. Submit a chain event or claim the next block; 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, block claim) are member-gated to the machine.
  • The explorer shows the chain; the proof is the offline verification above — don't take a UI's word for integrity when you can check the math.

Reference​

  • UI: apps/zeq-dev/public/apps/zeq-blockchain/
  • API: Chain API — blocks, events, state, GET /api/chain/seal
  • Protocols: Entangled state