LozealDocs
Open app

Proof

zkML and the proof

What is proven, what is not, and how to check it yourself.

The statement

Each seal is a public statement: the model with commitment W, run on feature vector D taken at anchor block B, produced score Y. The proof shows that statement is true without revealing W.

The four checks

  1. 1Package matches the on-chain seal: the package hashes to the sealHash stored in SealLedger.
  2. 2The zkML proof is valid: the verifier contract accepts the proof for these public instances.
  3. 3The model is the registered model: the model commitment equals the one registered for this agent version.
  4. 4The inputs match the anchor block: features recomputed from the anchor block equal the public inputs.

These checks run in your browser against the chain. Lozeal's servers are not asked for the answer.

Verify offline

The lozeal-verify tool ships with the source code in workers/zk. It fetches the seal from the API and checks it against the chain with your own RPC:

Command
cd workers/zk
uv run lozeal-verify seal <seal id> --api https://lozeal-api-production.up.railway.app --rpc <registry RPC URL>

What it does not prove

  • That the signal is correct.
  • That the prover did not see the score before sealing.
  • That every reading above the threshold was sealed.
  • That the inputs came from chain data inside the circuit. That is checked by recomputing them after opening.

Read How the proof works for the full table.