What to Store in a Blockchain Evidence Record
Create reviewable evidence records with query context, block identity, raw quantities and transformation references, without storing secrets or unnecessary personal data.
Overview
When translating these concepts into an integration, keep the scope described by the wallet history api with the result. The examples in wallet transaction history and smart contract event logs show how the same distinction affects neighbouring data questions.
An evidence record should let a reviewer understand how an answer was obtained. More data is not automatically better: the useful set is the minimum needed to reproduce the relevant observation and interpretation.
Capture context and provenance
Store network, method or evidence type, requested range, returned block references, observation time and relevant raw values. Link derived fields to decoder and calculation versions. Record source identity at an appropriate abstraction without copying credentials, session tokens or full sensitive request logs.
Worked example: a historical balance
A report says a wallet held 1.25 token units at a cutoff. Its evidence includes the contract, raw integer, decimals, selected block hash, cutoff-selection rule and observation method. That is more useful than a screenshot of 1.25 without any context. The screenshot can support review but cannot replace typed evidence.
Test reproducibility and retention
Ask whether another authorised reviewer could follow the same method and understand missing dependencies. Retain content digests where appropriate, but remember that a hash proves neither truth nor completeness. Define access and retention rules for wallet-linked records. Do not collect private keys or reusable authorisations simply to make a read-only report look thorough.
A practical acceptance test
Try reproducing a synthetic historical balance using only the exported evidence record. Check network, asset, raw amount, scale, cutoff rule and selected hash. Then remove one required field and verify that the review identifies the missing dependency. A content digest or screenshot alone must not be accepted as proof of a complete calculation.
Questions about the topic
Frequently asked questions
Does a digest prove a record is correct?
No. It helps detect content changes, not establish factual completeness.
Should evidence logs contain API secrets?
No. Store safe context and references without reusable credentials.
Standards & technical documentation
