A cryptographic register for proof-of-existence.
BitSeal records a signed Merkle root of a file at a specific moment. Files never leave the browser. The ledger stores the root, the leaves, a few bytes of metadata, and an Ed25519 signature produced by a key whose public half is published at /.well-known/bitseal-authority.json.
What BitSeal is, in one sentence
A register that, given a file, publishes a signed commitment stating that on a specific UTC timestamp it observed a file with a specific 32-byte BLAKE3 Merkle root.
What it is not
- Not a notary. A seal does not attest to authorship, identity, or the legal meaning of the content. It attests that a file hashing to the sealed root existed at the recorded time.
- Not a court. Admissibility depends on the jurisdiction and the underlying facts, not on the seal alone.
- Not a blockchain. There is no consensus, no coin, and no gas. One signer, published key, verifiable offline.
How to read these docs
Seal a file in the browser, verify it from the CLI, run through both paths in under five minutes.
The manifest spec, the Merkle fold, Ed25519 signing payload, ledger layout.
The three axes: ledger presence, signature, tree consistency. Each reported on its own.
POST /api/seal and GET /api/verify. Request, response, and error shapes.