Español

BLOCKCHAIN

Create a verifiable timestamp for an important document.

ForeverVault computes the SHA-256 hash of the exact file you stored and submits that fingerprint through OpenTimestamps for anchoring to Bitcoin. Anyone with that same file and the .ots proof can check the timestamp. The file is not published to Bitcoin.

See a Sample Certificate See Plans

Blockchain proof does not establish authorship, ownership, signature validity, notarization, legal validity, or that the document is the latest version.

How it works

The file is not published to Bitcoin. ForeverVault submits the SHA-256 of the file itself.

1. Fingerprint

ForeverVault computes the SHA-256 hash of the exact file bytes that were stored. Changing one byte of the file produces a different hash.

2. OpenTimestamps submission

The hash is submitted to OpenTimestamps, which combines many submissions into a cryptographic commitment.

3. Bitcoin anchoring

OpenTimestamps anchors that commitment to a Bitcoin transaction. Completion time can vary and is not guaranteed.

4. Independent verification

Anyone with the exact file and the .ots proof recomputes the SHA-256 of the file and checks the OpenTimestamps path to the Bitcoin timestamp.

The Bitcoin transaction alone is not normally sufficient to verify an individual raw hash without the OpenTimestamps proof path.

The certificate and proof file serve different purposes

The PDF certificate is a readable summary. The .ots file is the cryptographic proof. In the vault, the owner can download both for that item. Keep them with the exact file that was timestamped.

Sample certificate

This is a fictional sample document. It is not a live OpenTimestamps proof, and it does not depict a notarization.

Sample certificate — fictional estate — not a real Bitcoin timestamp

Blockchain Integrity Verification Certificate

Issued by ForeverVault to attest the integrity and timestamp of the document listed below using cryptographic hashing and anchoring on the Bitcoin blockchain via OpenTimestamps.

Sample — not a live proof
This certificate describes how to independently verify the hash of the document and its anchoring to Bitcoin, without requiring access to the contents of the vault.
Sample
Network: Bitcoin

Document & Vault Context

Document Name
Last Will and Testament — Margaret Elena Ruiz (sample)
Vault Item ID
FV-ITEM-SAMPLE-0001
File Type
PDF
File Size
1.42 MB (sample)
Version
Version 1.0 — fictional sample document
Anchor ID (ForeverVault)
FV-ANCHOR-SAMPLE
Cryptographic Hash of the Document (SHA-256)
Salt: None (standard raw SHA-256 hash)
c05edf41584d935b0f9174487d81d1850873169a1f72a4a9b8e3a495b615c4bb
This hash is a one-way fingerprint of the document. Any modification to the file will produce a different hash, causing verification to fail.
Note: ForeverVault uses OpenTimestamps to anchor this hash to the Bitcoin blockchain. The OpenTimestamps proof can be validated independently using the OTS proof file and any compatible verifier, without contacting ForeverVault.
OpenTimestamps Status: Sample only — not submitted to calendars. (Proof ID: ots_sample_0001)

Blockchain Anchor (Bitcoin)

Blockchain Network
Bitcoin
Anchor Status
Sample — not on chain
Block Timestamp (UTC)
2026-09-11 15:00:00 UTC (sample)
Bitcoin Block Height
Pending (sample)
Bitcoin Transaction ID (TXID)
Not provided — this is a sample, not an OpenTimestamps proof
OpenTimestamps Proof
Proof ID: ots_sample_0001
Status: Sample only
Certificate Generated (UTC) 2026-09-11 15:00:00 UTC
Issued By ForeverVault Blockchain Integrity Service support@forevervault.com https://forevervault.com
Independent Public Verification Instructions
Anyone with the original document and the .ots file can recompute the SHA-256 and check the timestamp without ForeverVault. This sample is not a live proof.
  1. Obtain the original document referenced as “Last Will and Testament — Margaret Elena Ruiz (sample)”.
  2. Compute the SHA-256 hash using any standard tool (e.g. shasum -a 256).
  3. Confirm that the computed hash matches exactly the hash shown under “Cryptographic Hash of the Document”.
  4. Visit the ForeverVault verification portal and enter the Verification Code to view current anchor status.
  5. Use the .ots file with a compatible OpenTimestamps verifier. That check uses the file and the .ots proof.
SAMPLE
Scan to open verification portal
VERIFICATION CODE FV-VFY-SAMPLE-0001
Or visit forevervault.com/blockchain/
Disclaimer: This is a sample certificate for a fictional estate. ForeverVault certifies that at the time of a real certificate, the hash value shown is computed for the referenced document and an OpenTimestamps proof is submitted for anchoring to the Bitcoin network. ForeverVault does not control the Bitcoin network or guarantee transaction inclusion times. This certificate does not constitute legal advice or a legal opinion. For legal questions regarding evidentiary use, consult a qualified attorney in your jurisdiction.

What it does not prove

  • It does not prove who created, signed, owned, or uploaded the document.
  • It does not prove that a signature or notarization is genuine.
  • It does not determine whether the document is legally valid or admissible.
  • It does not prove that this is the latest version.
  • Each changed version requires a new hash and proof.
  • It does not publish or encrypt the document. Vault storage is encrypted separately.
  • It is separate from ForeverBinder. ForeverBinder is the organized multipage report your chosen recipients can follow. See ForeverBinder.

Availability

  • All current Paid plans—monthly, yearly, and lifetime—include blockchain proof. Existing grandfathered Platinum subscriptions also retain blockchain-proof access. The Free plan does not include it.
  • There is no per-document or per-proof charge beyond the plan.
  • You can download the PDF certificate and the .ots file from the vault.
  • Pending means the fingerprint has been submitted and Bitcoin confirmation is not recorded yet. The vault shows Pending, or Pending verification, while the status is pending or submitted. The product does not use a status named Complete. When a Bitcoin transaction id or block height is recorded, the vault shows Verified and the certificate can say Confirmed on Bitcoin.
  • There is no button to regenerate a lost proof package. While the proof remains stored, you can download the PDF certificate and the .ots file again, including from archived certificate history after the item is deleted. If the stored proof is missing, the server may resubmit the same fingerprint when it refreshes the anchor. That is not a control you can press to replace a lost package.

These short lessons explain a fingerprint and a public timestamp in general terms. A new proof hashes the stored file. The owner can download the PDF certificate and the .ots file from the vault.

Two 1-minute lessons

Press Play. Your browser reads the lesson aloud. Turn the volume up.

What a SHA-256 hash is

42 seconds. A fingerprint of a file, not the file.

A hash is a fingerprint of a file. It is not the will itself.

0:00 / 0:42

What blockchain proof is

49 seconds. A public timestamp of the fingerprint.

Blockchain proof is separate. It is not ForeverBinder and it is not encryption.

0:00 / 0:49

Add independent timestamp evidence to an important document.

Start by protecting your documents in ForeverVault. Choose an eligible paid plan when you want to create blockchain proof.

Start Free See Plans
Download on the App Store Get it on Google Play