LozealDocs
Open app

How the proof works

What a Lozeal proof guarantees, and what it does not.

Each signal is a public statement: a model with commitment W, run on features D taken at anchor block B, produced score Y.

The proof shows that statement is true without revealing W. A smart contract checks the proof when the seal opens. You can run the same checks in your browser before that.

Guaranteed by the protocol

  • The score is the output of the registered model. zkML proof and the model commitment check.
  • Model weights stay private. Weights are a private witness.
  • The signal existed before the outcome. A timestamped seal tied to an anchored epoch.
  • A sealed signal cannot be changed. Keccak commitment over the proof package.
  • A sealed signal cannot be hidden. Seals that are not opened become Broken, permanently.
  • Creators cannot influence grading. The contract grades against a fixed price source.
  • Anyone can rebuild the full history. Every transition emits an event.

Not guaranteed

  • That a signal is correct. A proof shows honest computation, not a good model.
  • That the prover did not see the score first. The operator runs the prover in this version. Seal windows are short and the code is open.
  • That every reading above the threshold was sealed. There is no cryptographic coverage commitment yet.
  • That the inputs came from chain data. Features are recomputed by anyone after opening, not proven inside the circuit.
  • Who acts first after delivery. Renters receive signals at the same time. Faster renters may still act first.
  • Price manipulation at a mark. TWAP sources and a liquidity floor reduce it.
  • The trusted setup. KZG uses a public reference string from an open ceremony, not one made by Lozeal.

Contract owners can change the price source of a token. That affects seals in flight and is announced publicly. See Proofroom to check any seal.