Public proof should preserve privacy.
Useful public proof does not require placing the private file itself on a public ledger.
Verification
Understand how public proof can support independent checking without exposing private files or confidential content.
Public proof is designed to make evidence more independently checkable without forcing private content into public view. The public reference may support timing, anchoring, or integrity checks while the private evidence remains protected.
Core principles
Verification is useful because it is specific. These principles keep the record, the claim, and the limits separate.
Useful public proof does not require placing the private file itself on a public ledger.
A public anchor can support an integrity or timing reference, but the receipt and evidence context explain what the anchor relates to.
Evidence is stronger when a check does not depend entirely on the same private system that created or benefits from the record.
publicProof
Public reference
The public layer may contain a privacy-preserving reference. The private receipt or proof package explains the relationship between that public reference and the file or record being evidenced.
Blockchain anchoring
Anchoring can make a record harder to quietly rewrite later, but it must be interpreted through the relevant receipt and EviWrite verification context.
Boundary
A public proof item should not be treated as proof of ownership, permission, truth, or legal outcome unless those claims are separately supported.
Important
EviWrite verification helps check EviWrite-backed records, receipts, public proof, proof links, and evidential context. It does not replace legal advice, courts, regulators, investigators, expert witnesses, official registers, or factual review.