Why verification matters
Bid a 70B, serve a quantized 8B. Without verification, marketplaces converge to lemons.
The most profitable fraud in an inference market is quiet: quote one model class, serve a cheaper substitute, and pocket the difference. Outputs can look plausible while the cost and capability are not what the customer selected. Without verification, honest supply is forced to compete against an undisclosed downgrade.
Omnious separates the controls that affect Beta routing from review machinery that is still Shadow or Proposed.
The three layers
- Measured delivery in Beta. The router records time to first token, completion reliability, verification trust, and throughput. Those measurements feed the effective auction score; self-reported marketing claims do not.
- Operator evidence in Shadow. The repository contains canary tooling, claim records, trust events, and quarantine controls. They support supervised review, but Omnious does not describe an always-on automated audit network. Sampled re-runs against a reference deployment remain Proposed.
- Points-backed review in Shadow. Approved reviewer wallets can lock points against one receipt. An operator records an upheld, rejected, or ambiguous verdict under version
s0-2026.07.1. This is not a public bounty, does not move USDC collateral, and promises no token or conversion.
Economics under review
The implemented Shadow calculator sets the minimum reviewer stake at 25 GPUs, the provider-points reduction at a 250-GPU minimum or 25 times net earn, and the upheld reviewer credit at half that reduction. These terms are visible for inspection, but public eligibility, review service levels, appeals, and collateral terms are not approved.
- router/src/market/auction.ts measured service inputs in the Beta score
- router/src/trust/integrity.ts Shadow claims, evidence, challenges, and verdict records
- router/src/trust/challengeEconomics.ts versioned Shadow points terms
- mechanisms.json canonical availability and non-claims