Quick start

Seal one file. Verify it two ways.

Two paths, same manifest spec. Use the browser for interactive work, the CLI for files over 50 MB or automation.

In the browser

1.Open the sealer and drop any file up to 50 MB.
2.Your browser chunks the file at 64 KiB, hashes each chunk with BLAKE3, folds the Merkle tree.
3.Only the manifest (root, leaves, metadata) crosses the network. The Authority signs and records it.
4.Copy the Merkle root or download the PDF certificate.

Open the sealer

From the CLI

# install
pip install bitseal-sdk

# seal a file (any size)
bitseal seal ./contract_final.pdf

# verify a root offline, no network call
bitseal verify --root 6d56f7...  ./contract_final.pdf

The SDK produces the same root hash for the same bytes as the web sealer. Same spec, same output.

View the SDK

What to keep

The 32-byte Merkle root is the handle. If you keep it, you can always walk up to the ledger, the SDK, or a third-party verifier with the root plus the original file and ask: is this byte-for-byte the same thing that was sealed, and when was it sealed?