Guide

Portable proof packages

A proof package is a downloadable ZIP you can email, archive, or attach to a case file. It mirrors the live certificate with offline tools—so verification does not depend on DataSeal.net staying online forever.

What's in the ZIP

Download from a proof in your dashboard. The archive is a fixed snapshot at export time—ideal for long-term custody and offline review.

Offline ZIP

proof-package.zip

Package contents

Core files

certificate.htmlOffline-readable certificate
proof.jsonMachine-readable Merkle record
README.txtHow to verify locally
payload… (optional)By mode — see below

Works offline — long-term custody
Same cryptographic record as the live page

Provenance metadata

Optional author, tags, rights, license, and custom fields live with your certificate in DataSeal. A hash of that provenance is committed on-chain—the plaintext is not written to the ledger.

If those details matter for your records, download a proof package when you are ready. The ZIP keeps a copy of the metadata alongside the certificate so you are not relying on the live account alone.

File-by-file

certificate.html

Offline-readable certificate

Human-readable summary, Merkle diagram, and local hash validation. Encrypted packages also include local AES-GCM decrypt.

proof.json

Machine-readable Merkle record

Entry fields, fingerprint, provenance metadata, blockchain / Merkle data, verification flags, and optional share URL at export time.

README.txt

How to verify locally

Plain-text guide for that specific package—file list, mode notes, and verification steps.

Optional payload file

Included for Public (readable original) and Encrypted (ciphertext). Hash mode packages omit a payload—you must retain the original yourself.

How mode affects the ZIP

IncludedHashPublicEncrypted

Core files
certificate.html · proof.json · README
Readable payload
Original file or text
Ciphertext (.enc)
Encrypted archive

See proof modes for why these differences exist.

How to verify from a package

Extract & open

Unzip the package and open certificate.html in a browser.

Match the fingerprint

Use the built-in hash tool: paste text or choose the original file.

Inspect proof.json

Follow the README checklist for Merkle path and block header checks.

Decrypt if needed

Encrypted packages need your saved key. Prefer localhost over file:// for crypto APIs.

For a broader verification walkthrough, see Verify a proof yourself.

Live page vs package

Live link

Public proof page

Current while the share is active
Easy to revoke from the dashboard
Requires network to view