ONCHAIN STATE. OFFCHAIN EVIDENCE. ONE CLEAR VIEW.Frontend preview
Documentation /

Evidence & provenance

A status must be traceable to verifiable observations.

Required proof references

  • Proof-of-Reserve contract: The exact contract address that supplied the reserve observation.
  • Attestation transaction: The transaction hash anchoring the reserve attestation.
  • Auditor signature: The cryptographic signature payload and the authorized attestor identity.
  • Reconciliation context: The asset address, chain ID, checked-at time and observed block number.

Source: PDF p3 §9 and §7

Missing evidence is not a healthy result

The frontend shows missing contract references, transaction hashes, signature payloads and block/timestamp context as unavailable. It does not generate proof links or populate synthetic hashes.

The backend must identify authorized auditors, verify signatures and pin the onchain observation context. An explorer link alone does not prove a reserve statement. The full schema carrying §9 provenance is not included in the PDF’s §7 response example and must be finalized before integration.

Source: PDF p3 §9; implementation boundary

Audit view

Report views separate reserve reconciliation, six diagnostic checks, permission authorities and evidence provenance. A future live report must retain both the observed condition and the evidence supporting each non-trivial conclusion.

Source: PDF p3 §9; p4 §11 Phase 6