How results are verified
The verifier decides what counts, and the contract decides what is paid. Neither trusts the operator's machine.
The verification pipeline
- 01
Rules check
Before anything runs, the case is checked for wall-clock reads, randomness, network or file access, environment reads, inline assembly, code or storage rewrites, fuzz tests, and assertions that cannot fail.
- 02
Two pinned runs
The case runs twice on the job's snapshot with different seeds. Both runs must pass with identical results and gas, or the case did not reproduce.
- 03
Execution path
Line and branch coverage of the target, minus what the snapshot setup already covers, defines the case's path. Its hash is the fingerprint.
- 04
Duplicate check
A fingerprint already accepted on the job, in the verifier's records or on-chain, is a duplicate. Coverage jobs also require at least one branch no accepted case reached.
- 05
Eligibility and budget
The contract's isEligible check and the job's remaining budget are read before settling.
- 06
Sealed report, then payout
The case and its full trace are sealed to the sponsor's key first. Then the verifier calls recordAccepted, and the contract credits the reward.
What the contract enforces
- A job is funded in full when it is created. Paid work never opens on an unfunded promise.
- Each fingerprint is paid at most once per job.
- Only the job's approved verifier can record an accepted result, and only before the deadline.
- Holding requirements are checked on-chain at payout.
- Operators withdraw their own rewards. Earned rewards stay claimable after a job closes.
- The sponsor can reclaim only the unallocated budget, and only after the deadline.
- The budget counts what actually arrived, so fee-on-transfer tokens cannot inflate it.
ProbeJobs
Deployed on Robinhood Chain
0x75a7af44fe0117b1f5ff11eddad11fe1e0d34189Read the verified source on the explorer (opens in a new tab)Untrusted code, contained
Cases are code written by strangers, and job workspaces are written by sponsors. Both the CLI and the verifier run them in a sandboxed copy of the workspace.
- Foundry's ffi is forced off and file-system permissions are emptied, whatever the job's config says.
- RPC and fork settings are stripped, so cases cannot reach the network.
- Forge runs with a minimal environment: none of the operator's or verifier's secrets are visible.
- Runs time out after 180 seconds. Submissions are size-limited and rate-limited.
Trust assumptions
What you are trusting today, stated plainly.
- The verifier. One approved signer records accepted results. Its rules and fingerprints are deterministic and published, but there is no on-chain dispute process yet.
- Path, not intent. The verifier proves a case reproduces and reaches a new path. It does not judge whether a passing case is an important finding; sponsors set rewards with that in mind.
- The contract owner. The owner approves or revokes verifiers. It cannot move job funds.
Found a problem? Report it privately via a direct message to @probecli (opens in a new tab). See also the verifier docs.