Seal files & folders

Seal any files or folders, then verify, diff, and review their history.

# One-time: generate the root sealing keypair
provable init

# Seal a folder (recursive) or specific files
provable seal --mode=folder ./my-project
provable seal --mode=files a.txt b.txt

# Status, verify, diff, history
provable status ./my-project
provable verify ./my-project
provable diff ./my-project   # Monaco web diff for changed files
provable history my-project

Identity

Your identity is a BSV key pair. Each seal signs with a unique BRC-42 derived key, provably derived from your root identity key — a pure public-key computation any verifier performs locally, so no keyserver is trusted. The identity key travels in the seal metadata, and registration with provable.info uses BRC-103 mutual authentication. Register yours with provable register.

Portable proofs

Hand someone a proof they can verify without you.

# Export a bundle from the local store
provable proof export ./my-project -o my-project.proof.json

# Anyone can verify it standalone
provable verify --proof my-project.proof.json ./my-project

Features

• ✓BRC-42 key derivation — each seal uses a unique derived key, never reuses addresses
• ✓File-level Merkle tree — individual file hashes as leaves, tamper detection pinpoints which file changed
• ✓Public-math verification — hash, Merkle, signature, and key-derivation checks run locally with zero trusted parties; the chain check compares the anchored payload byte-for-byte via a public explorer
• ✓Layered verification — content hash → Merkle root → BRC-42 signature → block inclusion