Turn Any File or Folder into Verifiable ProofA file’s creation date is not proof.
It can be changed. A document can be replaced while keeping the same filename. Files can be added to or removed from a folder without leaving a reliable history.
That becomes a problem when an exact collection of files matters:
- Which version of a contract was delivered?
- What did a project folder contain at handover?
- Did this design, manuscript or dataset already exist on a particular date?
- Has an archive been changed since it was created? Beaver File Proof creates a portable, independently verifiable answer.
More Than a File Hash
Calculating a SHA-256 hash is easy. But a hexadecimal string alone is not a useful proof package.
It does not explain:
- Which files belong together
- How folders were organized
- When the package was created
- How the hash can be verified
- Whether an independent timestamp exists
- What another person needs to inspect Beaver File Proof turns selected files and folders into one structured evidence archive.
The package contains the original content, its folder structure, technical metadata and a SHA-256 manifest covering every included file.
Once completed, the archive is closed and no longer modified.
Independently Timestamped
Beaver calculates the cryptographic fingerprint of the finished evidence ZIP and submits a protected commitment to public OpenTimestamps calendars.
The original files are not uploaded.
Neither filenames, documents, images nor folder contents leave the Mac. OpenTimestamps receives only an opaque cryptographic commitment derived from the completed archive.
Public calendars combine many such commitments into a Merkle tree and anchor the resulting root in a Bitcoin transaction.
This allows thousands of independent proofs to share a single blockchain entry.
Why Confirmation Takes Time
The first OpenTimestamps receipt is initially pending.
The calendar must aggregate commitments, create a Bitcoin transaction and wait until that transaction has been included in a confirmed block.
Beaver remains open during this process.
The wait may take several hours, but it is an important part of the proof. The app is not simply adding the current time to a text file. It is waiting for independent confirmation outside the user’s Mac and outside the developer’s control.
After confirmation, Beaver creates the final delivery package.
One Package to Keep or Share
The completed package contains:
- The original evidence archive
- The included files and folder structure
- A SHA-256 manifest
- The completed OpenTimestamps proof
- A readable timestamp report
- Independent verification instructions The recipient does not need Beaver File Proof, an account or a cryptocurrency wallet.
The proof can be checked using the open OpenTimestamps protocol. When the evidence ZIP is selected for verification, its hash is calculated locally. The file itself is not uploaded.
Changing a single byte causes verification to fail.
Useful for Real Workflows
Beaver File Proof is not limited to one file type or industry.
It can document:
- Project handovers: Seal the exact source code, assets, documentation and configuration files delivered to a customer.- Contracts and offers: Preserve the precise document version that existed before it was sent, revised or signed.- Creative work: Timestamp designs, illustrations, manuscripts, music projects or other original material before publication or delivery.- Research and datasets: Create a verifiable snapshot of source data, calculations and results at a particular stage of a project.- Business exports: Protect accounting exports, reports, database snapshots and administrative records against unnoticed later modification.- Evidence collections: Bundle related documents, images, messages and notes into one package whose contents and structure can be verified together.- Software releases: Document the exact application, archive, disk image or source tree that was distributed as a release.### Why the Package Matters
Timestamping every file separately would produce an inconvenient collection of files and receipts.
Beaver instead seals the complete collection:
Files and folders
↓
Evidence archive
↓
SHA-256 manifest
↓
OpenTimestamps proof
↓
Bitcoin confirmation
↓
Portable proof packageThis establishes not only that individual files existed, but that this exact collection and folder structure formed one evidence package.
No Account, Subscription or Proprietary Server
Beaver File Proof does not depend on a developer-operated proof database.
There is:
- No Beaver account
- No subscription
- No cloud storage
- No upload of the original files
- No cryptocurrency payment
- No proprietary verification service The finished proof remains independently verifiable even if Beaver File Proof is no longer installed.
What the Proof Establishes
A valid proof demonstrates:
- The evidence archive has not been modified
- Its internal files match the recorded manifest
- The exact archive existed before the confirmed Bitcoin block time It does not automatically prove authorship, ownership, factual accuracy or the legal validity of a document. It also cannot guarantee how a particular court or organization will evaluate the material.
Beaver File Proof provides technical integrity and independently verifiable prior existence.
Select the files. Seal the package. Prove it existed.
Beaver File Proof is available for macOS as a one-time purchase, with no subscription.
https://apps.apple.com/us/app/beaver-file-proof/id6803359679
More tools are available at:
Top comments (0)