DEV Community

Cover image for How to Make Digital Content Verifiable
Christian Ahrweiler
Christian Ahrweiler

Posted on Originally published at Medium

How to Make Digital Content Verifiable

How to Make Digital Content Verifiable### A practical approach to preserving proof for webpages, files and photos

Digital information is easy to change.

A webpage can be edited after publication. A file can be replaced while keeping the same name. A photograph can lose its metadata, be recompressed by a social network or become separated from its source.

Sometimes you do not need to publish the content immediately. You simply need reliable evidence that a specific digital record already existed at a particular point in time — and a way to verify it later.

That is the purpose of the Beaver Proof app family.

It consists of focused apps for webpages, files and photographs, plus a free verifier. Each app is designed around the object being sealed, but all of them follow the same principle:

Preserve the data. Calculate its cryptographic fingerprint. Timestamp that fingerprint independently. Verify it whenever it matters.

Why several apps instead of one complicated tool?

A webpage, a project archive and a camera capture are not the same thing.

Sealing a webpage requires a browser-oriented capture workflow. Sealing a folder requires predictable packaging. Capturing a photograph should preserve the original bytes and may include camera or location information. Sharing a photo publicly needs a direct link that anyone can open without installing an app.

Putting all of those workflows into one application would make every task more complicated.

The Beaver Proof family therefore uses small, purpose-built tools. You choose the app that matches what you want to preserve, while the proof technology remains consistent underneath.

Beaver Page Proof: preserve what a webpage showed

Web content is temporary even when its URL remains unchanged.

A product listing can be updated. A price can disappear. Terms can be rewritten. A public statement can be corrected without leaving an obvious trace. Traditional screenshots help people see what was displayed, but a screenshot alone does not provide independent evidence of when that exact capture already existed.

Beaver Page Proof combines the captured page with an OpenTimestamps proof in a portable proof package.

This is useful for:

  • online listings and offers;
  • published statements;
  • product descriptions;
  • terms, policies and notices;
  • pages that may change or disappear. The result can be stored locally, archived with a project or sent to someone else for later verification.

Beaver File Proof: seal almost any digital material

Not every important record is a webpage.

A contract, source-code release, design file, video, audio recording or complete project folder may need evidence of prior existence. Beaver File Proof is the general-purpose member of the family.

Drop in a file or folder and the app creates a self-contained proof package with the material required for verification. The content itself is not uploaded to Beaver Proof. You decide where the package is stored and who receives it.

Typical uses include:

  • contracts and business documents;
  • source code and project releases;
  • photographs, video and audio;
  • research material and manuscripts;
  • archives and complete folders. The filename is not the proof. The cryptographic hash is. If even one byte changes, the calculated fingerprint changes as well and verification will no longer match the sealed record.

Beaver Photo Proof: create a portable camera record

Photography needs a more direct workflow than selecting an arbitrary file later.

Beaver Photo Proof captures photographs inside the app and creates a proof package containing the image record, timestamp information and available capture metadata. Location can be included when it is useful and intentionally enabled.

The result remains portable. It can be stored, transferred and independently checked like the other proof packages.

This makes Photo Proof suitable for photographs that may later support documentation, reporting, inspections or project records without requiring a permanent public page.

Beaver Proof Share: make a photo publicly verifiable

A portable package is ideal for archives and direct exchange, but it is not the natural format for a social post.

Beaver Proof Share addresses that gap.

The iPhone app preserves the untouched camera original and creates a separate sharing copy marked with a short visible ID:

BP SEALED · 7K4D9Q2MX8FR

The accompanying post, message or email can contain a direct link:

beaverproof.com/p/7K4D9Q2MX8FR

Anyone can open that link in a normal browser and inspect the current timestamp status. No account and no verifier app are required.

The original and full-resolution watermarked image are not uploaded to the public service. Only the proof data and a deliberately tiny 32 × 32 pixel preview are sent, allowing visual identification without publishing a usable copy of the photograph.

The photo can be shared while its Bitcoin timestamp is still pending. The same public link updates automatically after confirmation.

Beaver Proof Verifier: check proof packages for free

Creating a proof is only half of the workflow. Someone must also be able to check it later.

Beaver Proof Verifier is the common verification tool for portable Beaver Proof packages. Drop a package into the app and it checks whether the included content still matches its recorded cryptographic fingerprint and whether the OpenTimestamps proof is valid.

Verification is free because receiving a proof should not require purchasing the app that created it.

Public records produced by Beaver Proof Share do not need the verifier. Their direct links open in a web browser instead.

What OpenTimestamps adds

Beaver Proof uses OpenTimestamps to anchor proof records in the Bitcoin blockchain.

This does not mean that a photograph, document or archive is stored on Bitcoin. The files remain with the user. OpenTimestamps combines many document fingerprints into a Merkle tree and commits a compact result to a Bitcoin transaction.

Once confirmed, the proof demonstrates that the corresponding digital record existed no later than a particular Bitcoin block.

The timestamp does not depend on a date typed into a document, a local computer clock or a timestamp written only into file metadata. It can be checked against public blockchain data.

What a verified proof actually means

The distinction matters.

A valid Beaver Proof can confirm that:

  • the supplied data matches the sealed cryptographic fingerprint;
  • the timestamp proof is valid;
  • the sealed record existed no later than the confirmed Bitcoin timestamp.
    It cannot automatically confirm that:

  • every statement in a document is correct;

  • a photographed scene was not staged;

  • metadata reported by a device was accurate;

  • a file had never been manipulated before it was sealed;

  • the person presenting the proof created the original content.
    Beaver Proof provides evidence of existence and file integrity, not a universal certificate of truth.

Privacy by keeping the content under your control

The Beaver Proof apps are designed around hashes and portable proofs rather than central storage of user files.

Page, File and Photo Proof create packages that remain under the user’s control. Proof Share needs a small public record so that its link can work, but it does not upload the original photograph or a full-size public copy.

This separation reduces dependence on a central media archive while still providing a practical verification path.

Different workflows, one recognizable proof

The apps serve different situations:

  • Beaver Page Proof seals captured webpages.
  • Beaver File Proof seals files and folders.
  • Beaver Photo Proof creates portable camera-proof packages.
  • Beaver Proof Share creates publicly accessible photo proofs and sharing copies.
  • Beaver Proof Verifier checks portable proof packages for free. Together, they cover the path from private documentation to public sharing without forcing every user into the same workflow.

The goal is not to make people understand every detail of hashing, Merkle trees or Bitcoin transactions. The goal is to turn those mechanisms into a few clear actions:

Capture or select. Seal. Keep the proof. Verify when needed.

Learn more about the complete Beaver Proof app family at beaverproof.com.

Top comments (0)