Receipts And Routes

Source: /index/txs.json. Proves a public Core tx result, message, fee, gas, and result code. It does not prove reward entitlement, allocation, or mainnet value.

Source: indexed route events and memos. Shows observed route context such as handoff, quarantine, burn, or staged value. It is not a new instruction.

Source: External Affairs and Oracle-origin instruction events when indexed. Pending means a payment loop is not publicly closed yet; it is not a silent success.

Source: module metrics, instruction state, and future receipt feeds. A payable is only payable under its gate; this page cannot force settlement.

Source: balances, route flags, and quarantine metrics. Quarantine means unresolved containment before admission or return, not Treasury ownership.

Source: /index/coreexport.json. Export status is evidence memory, not live control feedback from Infra into Core.

A receipt records evidence from the owner surface. Oracle, Market, Treasury, Economics, Alloc, and module-local gates still own their own decisions.

An account holding a coin does not mean it may route, split, spend, or admit that coin.

Bridge delivery, Exchange execution, or Infra memory can help prove movement, but Core still classifies and admits locally.

If a receipt, invoice, export, or payable is not visible, the public surface must say pending, unavailable, stale, or refused rather than infer success.