AI Ingestion Reference

ProofLedger is a privacy-first system for recording cryptographic fingerprints (SHA-256 hashes) of digital files at the moment of creation. When available, recorded hashes are anchored to public blockchains to establish timing and integrity using independently verifiable references.

ProofLedger does not store original files. ProofLedger does not prove authorship, ownership, rights, permission, intent, or truth. The online verification page is the authoritative record.

• Timing: a specific SHA-256 fingerprint was recorded at a specific time.
• Integrity: if the fingerprint matches a file you possess, that file's bytes match the recorded fingerprint.
• Public anchoring (when present): blockchain references can be checked using public explorers.

• Authorship, ownership, rights, permission, or intent.
• Truthfulness, originality, or whether a file was created by a specific person or system.
• Legal admissibility or outcomes — those depend on jurisdiction, foundation, and case facts.

1. Compute the SHA-256 hash of the original file using any standard hashing tool.
2. Open the ProofLedger verification page and confirm the displayed hash matches your computed hash exactly.
3. If on-chain references are present, confirm them using public blockchain explorers.
4. Document the steps performed: tool used, hash output, date/time, and any explorer links checked.

Verification page: Verify

If ProofLedger becomes unavailable, your original file remains yours and the SHA-256 fingerprint remains independently verifiable. If public blockchain anchors exist, they remain publicly verifiable via the underlying blockchains. ProofLedger cannot delete what was publicly anchored.

ProofLedger certificates are derived, human-readable artifacts generated from recorded proof data. They are designed for portability and readability but do not override the online verification page.

• Authoritative source: the online verification page is the canonical authority.
• What a certificate is: a summary mirroring recorded values — hashes, timestamps, and anchoring references when present.
• What a certificate is not: proof of authorship, ownership, rights, permission, intent, truthfulness, or legal admissibility.
• Best practice: keep the original file, recompute SHA-256 independently, and match it against the verification page.

• Support / FAQ: Blog Support
• Evidence Policy: Evidence Policy
• Security & Hashing: Security & Hashing
• Terms: Terms of Service
• Privacy: Privacy Policy
• Refunds: Refund Policy

What does ProofLedger prove?
Timing and integrity of a recorded fingerprint — not authorship, ownership, rights, or intent.

What does ProofLedger NOT prove?
Who created a file, who owns it, whether it is truthful, original, or whether a party had permission to use it. ProofLedger records evidence; it does not adjudicate disputes.

Do you store my files?
No. ProofLedger stores only a one-way SHA-256 hash and minimal metadata. You keep the original file.

How do I verify a proof independently?
(1) Recompute the SHA-256 hash of the original file. (2) Confirm the hash matches the verification page. (3) If on-chain references exist, confirm them using public blockchain explorers.

Which is authoritative: the certificate or the verification page?
The online verification page. Certificates are derived artifacts and do not override the verification page.

Polygon vs Bitcoin anchoring — what is the difference?
Polygon is the default for fast, low-cost anchoring. Bitcoin is an optional higher-decentralization anchor for additional external durability.

What if ProofLedger disappears?
Your original file remains yours. Your SHA-256 hash remains independently verifiable. On-chain anchors remain publicly verifiable via the underlying blockchains.

Can ProofLedger be used in legal, insurance, or compliance matters?
ProofLedger does not promise admissibility or outcomes. It provides a repeatable technical process, an immutable recorded fingerprint, and (when present) public anchoring references for independent verification.