VERIFY WHAT THE EVIDENCE SUPPORTS

Verification and evidence

The verifier checks evidence offline. What can be established depends on evidence completeness, disclosure level and the actual verdict.

What the seven checks establish

CheckWhat is checked
1. Signature validityWhether the signature matches the known key history
2. Sequence continuityWhether sequences are continuous within the evidence scope
3. Hash-chain continuityWhether receipt hash links are consistent
4. Merkle inclusionWhether the Merkle commitment includes the receipt
5. RFC 3161 timestampWhether the RFC 3161 timestamp token is valid
6. Cost recomputationWhether disclosed pricing and variables reproduce the cost
7. Retail itemizationWhether disclosed customer retail itemization is consistent

Check 5 verifies the TSA timestamp. On-chain anchoring is checked separately under the anchoring specification; timestamp success does not mean the blockchain was checked.

Respect disclosure boundaries

Illustration only; no verification is executed here. Actual verdicts depend on the evidence bundle.

Public observerDISCLOSURE 01
01Signature validityAvailable
02Sequence continuityAvailable
03Hash-chain continuityAvailable
04Merkle inclusionAvailable
05RFC 3161 timestampAvailable
06Cost recomputationNot disclosed
07Retail itemizationNot disclosed

Public, supplier and customer views have different scopes. Checks may be skipped because data is not disclosed. Do not expose another party’s data to force a 7/7 result. Operator health endpoints are not seven-check verification reports.

Read verdicts and exit codes

VerdictMeaning
PASSThis check passed for the supplied evidence
FAILAn inconsistency or verification failure was found
SKIPPEDThe check could not complete due to disclosure or missing evidence

Verification failures exit 1; input or configuration errors exit 2. Ordinary mode can exit 0 with no FAIL even if checks were skipped. Strict mode exits 3 when SKIPPED remains. Period sampling must not be described as full verification.

Know the limits

  • Does not prove the identity of the upstream model; model names are input claims.
  • Does not establish absolute metering accuracy or contractual price fairness; external reconciliation remains necessary.
  • Does not prove every real event was captured or rule out missing exports.
  • Does not claim TEE or model-authenticity verification as an existing feature.

Search developer documentation

Enter a search term to find documentation.

Esc to close · No credentials are sent