# What is Proof of Existence? How to Prove a Document Has Never Been Altered — VerixID

Proof of Existence is a mathematical method to prove that a file existed at a specific point in time and has never been modified. Learn how SHA-256 hashes and immutable ledgers work with VerixID.

---

## Navigation

- **Submit**: https://verixid.com/en/#dropzone
- **Verify**: https://verixid.com/en/verify/
- **COA**: https://verixid.com/en/coa/
- **Docs**: https://verixid.com/en/docs/
- **Language Switcher (ID)**: https://verixid.com/learn/proof-of-existence/
- **Issue COA**: https://verixid.com/en/coa/

---

## Article Metadata

- **Category**: Foundations
- **Title**: What is Proof of Existence? How to Prove a Document Has Never Been Altered
- **Lead**: Any digital file can be altered without leaving a visible trace. *Proof of Existence* is a mathematical method to prove that a file existed at a specific point in time and has never been modified since. Not a claim. Not a promise. Pure mathematics.
- **Badges**: `Foundations` | `SHA-256 Hash` | `Zero-Custody`
- **Read Time**: ⏱ 8 min read
- **Date Published**: 2026-03-29
- **Date Modified**: 2026-03-29
- **Canonical URL**: https://verixid.com/en/learn/what-is-proof-of-existence/
- **Keywords**: proof of existence, document integrity proof, digital document authenticity verification, SHA-256 hash, digital fingerprint, immutable ledger

---

## Main Content

Imagine this scenario: you send a financial report to a client on March 1st. Two weeks later, the client claims the figures in the report differ from the version they originally received. Who is telling the truth?

Without the right system in place, this question cannot be answered objectively. Emails can be edited, file metadata can be spoofed, and operating system modification timestamps can be altered by anyone within seconds. **Proof of Existence** solves this problem — in a way that relies on no one's authority or goodwill.

> **Definition**  
> **Proof of Existence** is a technique that enables someone to prove that a file existed at a specific point in time *and has never been altered since* — without ever revealing the contents of the file to anyone. The final authority is mathematics itself.

---

### The Problem It Solves

File metadata — including the "created date" and "modified date" visible in Windows Explorer or macOS Finder — **can be changed by anyone**. This is not a security flaw; it is simply how operating systems work.

> **Crucial Fact**  
> File modification dates, email timestamps, and document metadata are not proof of integrity. All of them can be manipulated without leaving any trace detectable by standard tools.

Proof of Existence replaces trust in metadata with trust in mathematics. Instead of asking *"when was this file last modified?"* the system asks *"does this file's mathematical fingerprint match the record stored on the ledger?"*

---

### How It Works: SHA-256 Hashes as Digital Fingerprints

At the core of Proof of Existence is the cryptographic hash function. VerixID utilizes **SHA-256** — the same standard relied upon by global banking systems, governments, and internet infrastructure.

An SHA-256 hash possesses three mathematical properties that make it ideal as a file fingerprint:

* **Deterministic**: The exact same file always yields an identical hash — on any computer, at any time, by anyone. No external variables affect the output.
* **Avalanche Effect**: The slightest change — a single character, one pixel, one byte — results in a completely different hash. There is no pattern or correlation between minor edits and the resulting hash output.
* **One-Way / Irreversible**: It is mathematically impossible to reconstruct the original file from its hash. This is what makes Zero-Custody technically possible: the system stores hashes without ever being able to "read back" the file contents.

Below is an illustration of how changing a single character results in an entirely distinct hash:

```text
SHA-256 · "Q1 2026 Report.pdf" — original file
a3f2c8e1d94b07652fe38c1a90b74d2e5c683f1a2b094e7c8d5f3a6b1e2c9d40f

SHA-256 · the same file after modifying a single character
7b19e4f2c83d06741fe27b0a81a63c1d4b572e0f1a983d6c7e4b2a5f0d1e8b3c9