Freeze the ticket
The requester deposits the reward and commits the exact source, benchmark, verifier, policy, and deadline.
A requester freezes a benchmark and verifier. A builder submits an artifact. Independent critics replay it, challenge it, and sign the result before settlement.
“Improve this 10×” becomes a content-addressed source tree, baseline, verifier, workload, metric, environment, and acceptance rule. The phrase is not left to a subjective review.
{
"protocolVersion": "proofmesh/0.1",
"baseline": "sha256:…",
"verifier": "sha256:…",
"benchmark": { "metric": "median_guest_cycles", "repetitions": 7 },
"correctness": "differential-trace-equal",
"acceptance": { "maximum": 100000000 }
}The requester deposits the reward and commits the exact source, benchmark, verifier, policy, and deadline.
A builder submits a patch, reproducible build manifest, measurements, and proof bundle.
Critics check semantics, performance, security, dependencies, and reproducibility from independent environments.
Verdicts are committed before other reports are visible. A replayable counterexample can open a challenge window.
A quorum of signed attestations settles the ticket. Review fees, failure bounties, bonds, and the builder reward follow the policy.
Run the artifact in a fixed sandbox and compare outputs, guest traces, state digests, and resource counters.
Several critics run the verifier independently. Disagreements escalate to additional replay or a challenge game.
zkVM, SNARK, or STARK bundles can prove a specified computation. They do not make an ambiguous benchmark precise.
The security comes from the frozen verifier and the critic protocol, not from a coin. The first release uses inspectable credits or escrow records. A native staking asset can come later, after demand, dispute rates, and critic economics are measurable.