Provable
Proof That Travels
Forms whose every response is sealed on the BSV blockchain, and a CLI that seals any build, release, or folder. Each seal is a proof anyone can check — no vendor that has to outlive your evidence.
Provable Forms
Build a form, publish it, collect responses. Every response is validated against the published version, hashed, and sealed on BSV, and each respondent gets a receipt.
- ✓Visual builder, 23 field types, 33 templates
- ✓Link, iframe, or embed script
- ✓Signed webhooks, CSV/JSON export, REST API
Provable CLI
Seal any build, release, or folder into a signed proof bundle. Anyone verifies it with the CLI — offline if needed, no account. You sign; provable.info pays to anchor.
- ✓Proof bundles that travel with the artifact
- ✓Verification as policy: pinned key, max age, min version
- ✓Stateless CI with one secret
More Ways to Seal
Seal hashes and documents over REST, from the browser, or under your own BSV identity.
Seal any file or folder with Merkle roots, BRC-42 derived signing keys, and on-chain proofs. Pin the publisher key and verification becomes policy.
Seal and verify via REST. Upload files or submit pre-computed hashes — verify is always free.
Contracts, reports, evidence — seal and verify any document from the browser. Verification is free, forever.
How It Works
Seal
Form responses or files are hashed into a Merkle root and signed. With the CLI, hashing happens on your machine — file contents stay there unless you choose to publish them.
Anchor
Each seal is anchored on the BSV blockchain in its own transaction. provable.info pays and broadcasts — no wallet, no funding.
Verify
Anyone can check a seal. CLI proof bundles verify offline with no account and exit non-zero on failure, naming the tampered file. Every Forms response has a public seal record.
Recent Activity
auto-refreshes every 15sLoading activity…