Proof & records
Inspect receipts, ownership and source history
Follow a financial result to its original participants, value sources and causal predecessors.
Begin with the event
- Open the recorded operation
Use account history, the supported receipt link or its retained recovery result.
- Read the actual participants
Check sender/recipient identity coordinates, amount, rail and event type.
- Inspect source relationships
Open the carried predecessor/funding relationships and complete original where available.
- Retain the right evidence
Keep the original and exact operation reference, not only its chart or screenshot.
Separate evidence roles
| Evidence | Role |
|---|---|
| Original financial source | Admitted result with its source/participant bindings. |
| Wallet or Market export | A retained observation of original returned rows; not newly issued financial authority. |
| Ownership history | Prior and current supported transitions; old ownership does not authorize a new transfer. |
| Public Ledger view | Deliberately public source/evidence within its disclosure scope. |
| Chart | Supported calculation/observation, distinct from execution price or current spendability. |
Trace funding without rewriting it
An original transfer may record exact funding allocations. The interface can also calculate pooled oldest-available-first FIFO attribution from admitted history. Those are distinct evidence roles: the calculation explains its basis and relationships, while the original allocation remains unchanged. A missing predecessor or an unavailable quote cannot be filled with a fabricated source. Preserve exact units and participants across inspection.
Read causal and human time
Local time makes an event understandable. Native history and admission preserve their Kai/KKS temporal coordinates and required KaiSigil proof. Wall-clock time, file modification time or server arrival order cannot replace a verified causal predecessor. A genuine old original proves its recorded evidence; fresh ownership, consumption or unspentness needs its actual current source.
Share the intended scope
A short receipt link identifies an exact supported source. The recipient should inspect the original and match the intended event rather than trust the appearance of a success page. Public sharing does not automatically disclose the whole private account archive. A complete account proof does have a broad reviewed scope, including balances, holdings and full transaction history. Choose that disclosure deliberately and keep private originals private.
Implementation sources
Inspect the exact path.
Source links retain revision 6c5d582. Read the documented operation and assessment scope alongside its code.