DefaultVerifier
Specifications

Default Settlement Specifications

Technical standards and reference documentation for settlement receipts, verifier interfaces, continuity checks, and execution-boundary evidence.

Naming hierarchy — do not collapse these

  • Default Settlement — the trust/evidence system and company-level architecture.
  • DefaultVerifier — the deterministic verification engine inside that system.
  • SAR — Settlement Attestation Receipt; the core evidence object Default Settlement authored.
  • Continuity — the long-term trust/history layer built from repeated verified SARs.
  • Trust Passport — the public trust-history surface generated from verified SAR history.
  • Explorer — the public inspection surface for receipts, agents, and evidence.
  • SAR-402 — an x402-specific profile of SAR, not the whole system.
SAR-402 · Path B

SAR-402 recording attribution (Path B)

SAR-402 has three paths. Path A records resource-server delivery evidence into a SAR receipt structured for public inspection. Path B adds a recording-attribution wrapper. Path C runs a deterministic conditional-release evaluation against a committed acceptance spec and signs the result in a Continuity Evaluation Receipt (ds.continuity_evaluation.v0.1). This section documents Path B; the live receipt model is documented in Continuity v0.1.

  • Wrapper purpose — DefaultVerifier signs the recording wrapper around the SAR-402 receipt so a third party can confirm DefaultVerifier — not the submitter alone — recorded the receipt. The signature attributes recording only; the resource server remains the deliverer and verifier_has_execution_authority stays false.
  • Recording key iddefaultverifier-recording-ed25519-1.
  • Public key location/.well-known/sar-keys.json.

Authority boundary. Path B attests only that DefaultVerifier recorded this receipt. It does not attest to delivery, payment execution, access authorization, release control, legal payment finality, or mainnet settlement.

Reference Surfaces