Verify a Sealway proof, without Sealway

Any Sealway proof can be verified independently. The evidence file contains all the technical elements needed.

The tools

Each one runs on your device and answers a different question.

• Verify a proof folder The whole folder, checked end to end: the files against their fingerprints, the Merkle tree, the qualified timestamp and the public blockchain anchors. Takes: A .zip proof folder Verify a folder →
• Verify a timestamp token One RFC 3161 token on its own, read field by field: the sealed date, the fingerprint it seals and the provider that issued it, with the raw structure alongside. Takes: A token, base64, PEM or hex Verify a token →
• Verify a Merkle tree The arithmetic on its own: rebuild a root from a list of digests, or check that one leaf belongs to a tree whose root you already have. Takes: Hexadecimal digests Check a tree →

What the tools check on your behalf

1. 1

   Get the evidence file

   The PDF + timestamp token has been delivered to you or is available in your account.

2. 2

   Recompute the file fingerprint

   On your machine, recompute the SHA-512 fingerprint of the original file.

3. 3

   Verify the timestamp token

   Submit the token to the qualified provider listed in the file. The verification confirms date, time and sealed fingerprint.

This verification does not require Sealway. It is designed to remain valid over time, independently of the service.