Concepts

Evidence is the product boundary

Learn how source receipts, USC proofs, registry state, and typed packets combine into a verifiable underwriting input.

v0.1 · testnet

Evidence lifecycle

The source escrow emits OrderGuaranteed, OrderCancelled, OrderDisputed, or OrderSettled.
The worker waits for the configured confirmation depth and identifies the receipt-local log position.
The Attestcoin proof builder returns a Merkle and continuity proof for the source transaction.
TradeEvidenceUSC verifies receipt success, trusted emitter, exact event shape, and replay status on Creditcoin.
The worker persists the stage and exposes only sanitized status through the read-only API.

Receipt-local log index matters

Explorers may display a block-wide log index. USC verification requires the event position inside the transaction receipt. LoomCredit stores and revalidates the receipt-local index before proof submission; using the explorer index can select the wrong event or fail verification.

{
  "blockHeight": 11443299,
  "txIndex": 106,
  "logIndex": 1,
  "proofStatus": "LIVE_VERIFIED"
}

EvidencePacket contract

Field group	Why it exists
Identity	orderId, evidenceId, source and execution networks bind the packet to a specific obligation.
Commercial facts	Order value, guarantee, token, deadline, and commitments are decoded facts, not model guesses.
Lifecycle	Facility state and settlement/dispute counters constrain whether underwriting is valid.
Capacity	Total and available sandbox liquidity keep off-chain policy aligned with RiskGuard.
Proof	LIVE_VERIFIED is the only status permitted to reach a real model or signer.

Live versus fixture data

Documentation is generated from the current repository contract. For the recorded testnet evidence, inspect the live proof console.