Proof Of Inference And Proof Of Useful Work¶

Last updated: 2026-06-28

Proof of Inference and Proof of Useful Work are Cortensor's quality and verification concepts. They explain why the network does not treat a single model output as automatically trustworthy.

PoI checks execution Correctness and consistency

Proof of Inference focuses on whether an inference task ran and whether results can be compared across participants or expected behavior.

PoUW checks usefulness Relevance and quality

Proof of Useful Work focuses on whether the output is useful, coherent, relevant, and valuable for the requested task.

Validators add judgment v1 / v2 / v3

Validator v1 regulates network task behavior, validator v2 adds quantitative checks, and validator v3 adds qualitative checks.

Products expose verdicts validate / factcheck / Corgent

Higher-level APIs package validation into verdicts, scores, reasons, evidence, and retry guidance.

Mental Model¶

Concept	Meaning
Proof of Inference	Evidence that an inference task was executed and that results can be compared across participants or against expected behavior.
Proof of Useful Work	Assessment that the work was useful, relevant, and high quality enough for the task.
Redundancy	Running a task through more than one miner/session to improve confidence.
Reputation	Long-term signal from node behavior, stats, and validation outcomes.
Verdict	Product/API output such as `VALID`, `INVALID`, `RETRY`, or `NEEDS_SPEC`.

Implementation Anchors¶

Area	Why it matters
`SessionQueueValidation`	Task validation lifecycle.
`NodeStats` and `NodeReputation`	Network memory of participant behavior.
`ValidatorStats`	Validator-side performance and activity signals.
`QuantitiveStats` and `QualitativeStats`	Numeric and qualitative scoring surfaces.
`/api/v2/validate` and `/api/v3/validate`	Router validation routes used by higher-level products.
Corgent/Bardiel validation	Product-facing packaging of validation and arbitration concepts.

Validation Flow¶

flowchart LR
  Task["Task"]
  MinerA["Miner A result"]
  MinerB["Miner B result"]
  Validator["Validator / quality policy"]
  Reputation["Stats and reputation"]
  Verdict["Result or verdict"]

  Task --> MinerA
  Task --> MinerB
  MinerA --> Validator
  MinerB --> Validator
  Validator --> Reputation
  Validator --> Verdict

Verification Boundaries¶

PoI and PoUW describe validation concepts and network workflows. Cryptographic proof formats, attestations, ERC-8004 artifacts, slashing behavior, and binding arbitration depend on the exact implementation and deployment.

Product Fit¶

Cortensor can route a task through redundant execution and validation policies.
Validation endpoints help applications check results, claims, or proposed actions before relying on them.
Reputation and stats provide network-level signals for operator and product workflows.