How VerifyFirst Works
A Secure, Three-Layered Proof Process
VerifyFirst combines local hashing, blockchain anchoring, and business logic to give you tamper-proof document verification.
Step-by-Step Process
1. Local Hashing
Compute a SHA-256 hash of your document on your device—no file leaves your control.
2. Business Logic & Timestamp
Attach an optional cover letter, set an expiration period, then timestamp via our API.
3. Blockchain Anchoring
Anchor your hash to the Bitcoin blockchain for immutable proof of existence.
Developer API & Webhooks
Seamlessly integrate timestamping, verification, revocation, and expiry alerts into your application.
Timestamp API
POST /api/timestamp — Upload your document hash and optional cover letter to generate a timestamp and proof file.
Verify API
GET /api/verify/{proofID} — Validate a proof file or document hash and retrieve verification status and details.
Revoke API
POST /api/revoke — Invalidate an existing proof when rights or ownership change; provide proofID to revoke.
Notification Webhook
Configure webhook_url and alert_period (in days) to receive callbacks before or on document expiration.
White-Label Verification Portal
Offer your customers a branded verification experience at verify.yourdomain.com, complete with your logo, colors, and custom messaging.
Blockchain Anchoring & OpenTimestamps
When you submit your document hash, VerifyFirst groups it with other hashes in a Merkle tree and anchors the Merkle root on the Bitcoin blockchain using the OpenTimestamps protocol.
- Merkle Tree: Efficiently bundles multiple document hashes into one root hash, minimizing on-chain data.
- OpenTimestamps: A lightweight protocol that batches proofs into Bitcoin transactions, ensuring decentralization.
- Public Verification: Anyone can verify the timestamp by reconstructing the Merkle path and checking the blockchain entry.
Ready to Secure Your Documents?
Sign up and start timestamping in minutes—no crypto knowledge needed.
Get Started