Omniousdocs
Market integrityShadow

Becoming a challenger

The approved-challenger registry, wallet-signed filings, stake quotes, and reading your ledger.

Owner
Trust & Safety
Version
s0-2026.07.1
Verified
2026-07-13

Challenging is a Shadow operator program: filings are accepted only from wallets in the approved-challenger registry. There is no public application, reward entitlement, or permissionless adjudication. This page documents the implemented reviewer path, not a customer feature.

Getting approved

The registry is seeded by the operator (modelIntegritySeedChallengersin the router config), and wallets can be added or retired through the admin surface. You can check any wallet's standing at GET /v1/model-integrity/challengers/:wallet. Addition or retirement is an operator decision based on reproducible evidence work; the endpoint is not an open enrollment surface.

The filing loop

  1. Find a suspect receipt. Integrity receipts, drift signals from the verification pipeline, and your own paid probing are all fair game. What you are looking for is a specific fill whose output does not match the claimed model.
  2. Quote your stake. GET /v1/model-integrity/challenges/quote returns the stake for that receipt before you commit: max(25 GPUs, 1x its base points earn). Base earn is 100 GPUs per $1 charged. The server also checks it against your available balance (settled minus locked).
  3. Sign and file. Sign the ModelChallenge EIP-712 payload (domain Omnious Model Integrity) with your challenger wallet and POST /v1/model-integrity/challenges. Your stake locks.
  4. Resolution. An operator records the verdict. Upheld pays you half the slash; rejected burns your stake; ambiguous returns it. The mechanics are on The three verdicts.

Reading your ledger

GET /v1/points/:walletsurfaces your challenge ledger alongside your volume points: open, won, and lost counts, locked stake, earned bounties, forfeited stakes, and net. Every number is derived from the challenge rows themselves, so your ledger and the market's books cannot disagree.

one live challenge per receiptIf a receipt already has an open or upheld challenge, yours will be rejected at the door. Rejected and ambiguous verdicts free the receipt again, so a badly argued filing by someone else does not permanently shield a cheat.
As a challengerFile narrow and evidenced. The stake pricing means scattershot filing is a losing strategy by design; one reproducible mismatch beats ten hunches.
As a providerThe registry means accusations come from identified, staked wallets with track records, not anonymous spam. Your defense is the receipt itself and the verification record around it.
where this lives in code