Verify a result
Every Zeq result carries a ZeqProof — a signed statement binding the value, the equation, the precision, and the Zeqond together. Verifying re-checks that binding, so you never have to trust the machine that computed it. This guide verifies a result you were handed.
What you're checking
A compute returns the number and a verify object with everything a check needs: the operator
chain, the inputs, the result digest, the Zeqond, and the signature. That bundle is the
envelope — it proves itself.
Verify it
Hand the result's proof back to the framework — any node re-checks it identically:
curl -sX POST https://zeqsdk.com/api/zeq/verify \
-H "Content-Type: application/json" \
-d '{ "zeqProof": "…", "value": 2954.0077, "operators": ["KO42","GR37"], "zeqond": 2296532592 }'
# → { "verified": true, … }
From the terminal, the CLI wraps the same check in one command:
zeq verify ./result.json # re-checks the ZeqProof from the envelope alone
Because the check is deterministic and the signature is verifiable offline, a true means the result
is genuine no matter where it came from — the whole point of a proof-carrying result.
Read next
- Proofs — what a ZeqProof binds together, and why it holds.
- The envelope — the receipt the proof travels in.
- Conformance & verification — verifying a whole machine, not just a result.