Paxiom
Paxiom · Standard Specification Sheet
Trust States & Precedence
All sixteen verification verdicts and deterministic evaluation order.
Sheet PXM-RC-101· paxiom.receipt.v0· v0.2.0

Sixteen deterministic verdicts. Strict top-to-bottom precedence.

A conforming paxiom.receipt.v0 verifier consumes a receipt (and, where supplied, the delivered output and expected seller keys) and emits exactly one trust state plus a structured per-check breakdown. Trust states are the honesty contract: they separate what was independently verified from what was merely claimed.

01 · The Enum

All sixteen trust states.

Trust stateMeaning
verifiedEverything the offline verifier can check passed, optional signer pinning matched, and settlement is either counter-attested by a trusted verifier key or not an unconfirmed on-chain claim.
valid_signature_onlySignature is valid, but the verifier could not reach verified for a non-fatal reason (e.g., delivered output was not supplied, or settlement.status = unknown).
schema_invalidReceipt does not conform to paxiom.receipt.v0.schema.json.
unsupported_formatreceiptVersion is not paxiom.receipt.v0.
invalid_signatureEd25519 signature does not verify against the embedded public key over the canonical signing input.
unauthorized_issuerSignature is mathematically valid, but signature.publicKey is not in expectedIssuerPublicKeys (from the seller's HTTPS /.well-known/x402-keys.json) or payTo mismatches expectedPayTo.
request_binding_missingRequired request binding fields absent or malformed.
payment_binding_missingRequired payment binding fields absent or malformed.
output_hash_mismatchSupplied output's jcs-sha256 or raw-sha256 digest does not equal delivery.outputHash.
settlement_claimed_not_checkedSignature and output hash verified, but the receipt asserts an on-chain settlement that this verifier did not independently confirm.
settlement_failedsettlement.status = failed.
proof_not_providedEvidence array is empty or all not_provided (informational in check breakdown; does not by itself block verified).
proof_unavailableAn evidence record references an external artifact the verifier could not retrieve.
proof_invalidAn evidence record was retrieved and failed verification.
expiredexpiresAt is present and in the past relative to verifier evaluation time.
errorThe verifier itself encountered an unexpected failure (e.g., nesting depth > 256 or I/O error).
02 · Precedence

Resolution order (offline verifier).

Evaluate top-to-bottom and return the first rule that applies. This guarantees, for example, that key-substitution attacks surface as unauthorized_issuer and tampered payloads always surface as output_hash_mismatch:

  1. Verifier exception → error.
  2. receiptVersion unrecognized → unsupported_format.
  3. Schema invalid → schema_invalid.
  4. Ed25519 signature fails over canonicalize({ receiptVersion, payload }) → invalid_signature.
  5. expectedIssuerPublicKeys or expectedPayTo supplied and mismatched → unauthorized_issuer.
  6. expiresAt present and past → expired.
  7. request bindings missing or malformed → request_binding_missing.
  8. payment bindings missing or malformed → payment_binding_missing.
  9. Output supplied and its canonical or raw hash ≠ delivery.outputHash → output_hash_mismatch.
  10. settlement.status = failed → settlement_failed.
  11. Evidence retrieved and invalid → proof_invalid; referenced but unreachable → proof_unavailable.
  12. settlement.status ∈ { claimed_not_checked, verified_settled } without a pinned key in trustedVerifierPublicKeys (or alias trustedPaxiomPublicKeys) → settlement_claimed_not_checked (issuer self-assertions never self-promote to verified settlement).
  13. Output not supplied, or settlement.status = unknown → valid_signature_only.
  14. Otherwise → verified.
Counter-Attestation Upgrade

Calling the free public reference endpoint POST https://api.paxiom.org/v1/receipt/verify-live verifies canonical Base USDC Transfer event logs directly on-chain and returns a counter-signed Payment-Receipt verifiable offline when the published verifier key (/.well-known/x402-keys.json) is passed in trustedVerifierPublicKeys.

03 · Test Vectors & Breakdown

Fixture outcomes & per-check diagnostics.

Receipt fixtureOutput suppliedExpected trust state
valid.receipt.jsonvalid.output.jsonverified
valid.receipt.jsonoutput-mismatch.output.jsonoutput_hash_mismatch
valid.receipt.json(none)valid_signature_only
settlement-claimed-not-checked.receipt.jsonvalid.output.jsonsettlement_claimed_not_checked
{
  "trustState": "settlement_claimed_not_checked",
  "checks": {
    "schema": "pass",
    "signature": "pass",
    "outputHash": "pass",
    "requestBinding": "pass",
    "paymentBinding": "pass",
    "settlement": "claimed_not_checked",
    "proof": "not_provided"
  },
  "summary": "Signature and output hash verified. Receipt claims an onchain settlement that this verifier did not check."
}