Skip to content

Verifier

How results are reproduced, how duplicates are detected, and why cases fail.

The verifier is the part of PROBE that decides what counts. It replays each submitted case in a pinned environment and compares the result. If it cannot reproduce the result exactly, the case does not qualify.

What is pinned#

  • The chain snapshot named by the job, including block number and block time.
  • Contract code and storage at that snapshot. No live RPC calls.
  • Randomness, which must come from a seed recorded with the case.
  • The runner version that executed the case.

Verdicts#

Accepted#

The case reproduced and meets every acceptance rule. It asserts a concrete outcome and its fingerprint is new on this job.

Duplicate#

The case reproduced, but its execution fingerprint matches a case already accepted on the job. The earlier case keeps the reward. Changing an amount or a variable name does not change the fingerprint if the code path and effect are the same.

Failed verification#

The verifier got a different result, or the case breaks a rule, for example by reading the machine clock, using unseeded randomness, or calling the network. The verdict always names the reason.

Fingerprints#

A fingerprint summarizes the path a case took through the hook and the state it changed. It is shown shortened, for example 7c1e…a04f. Two cases with the same fingerprint are the same finding.