Untch docs

Start here

Untch documentationQuickstartWhat Untch is

Concepts

SpendIntentPolicyPreflightEnforcement modesReceipts and proofTrust Bureau

For operators

DashboardPolicies (operators)EscalationsControl channelsVault

For agents

ASP overviewASP toolsx402 paymentsUntch GuardLifestyle and Launch Pack

Reference

NetworksContractsPricingErrors

Security

InvariantsThreat model

Decision and verification hashes anchored on UntchReceipts.

Receipts and proof

Every meaningful decision can become a receipt: a hash-only record anchored on X Layer. Payloads stay off-chain. Public proof is the hash and metadata on UntchReceipts.

Receipt kinds

KindMeaning
DecisionPreflight outcome (approve, block, escalate path)
VerifyDelivery verification result
ScoreTrust Bureau epoch root
AuditDispute packet or reconcile report anchor

Proof tiers

TierStatus
T0 SchemaLive. Delivery payload matches committed acceptance criteria.
T1–T4Documented ladder. Higher tiers return honest not-implemented until shipped.

Policy can require a minimum tier by amount. If required tier is above available tier (today 0), preflight escalates with ESCALATED_PROOF_TIER.

Public explorer

www.untch.xyz/explorer lists:

  • Sample settled and anchored transactions
  • PolicyRegistry, SpendIntentRegistry, UntchReceipts, VaultFactory addresses (mainnet and historical testnet)

Writer status (mainnet)

Mainnet UntchReceipts uses a writer bootstrap with a timelock. After Phase-1 deploy, writer authorization completes only after the delay. Reads and addresses are correct throughout. Continuous anchoring needs the writer live.

Related