BitProof anchors content hashes to Bitcoin for independent timestamp evidence.
The scenarios below show where existence and integrity proof materially changes decisions.
When proof matters
Journalism
A government agency edits a web page after a news story breaks
A journalist notices a policy page has been quietly changed. The original version contradicts the agency's public statement. But screenshots can be fabricated, and the Wayback Machine may not have captured it in time.
With BitProof: The journalist archived the page before the edit. The .bitproof bundle contains the screenshot, HTML, and PDF, all anchored to a specific Bitcoin block. The proof is independently verifiable. No one needs to trust the journalist, BitProof, or any third party. The math speaks for itself.
Research
A researcher's priority is disputed after publication
Two labs publish similar findings weeks apart. The second lab claims they had the results first but were slower to publish. Without evidence, the dispute becomes political.
With BitProof: The first lab timestamped their dataset and analysis code before submission. The .bitproof bundle proves the work existed in its final form before the other lab's publication date, anchored to a Bitcoin block instead of a journal's timeline alone.
Legal
A contract dispute hinges on what the terms said at signing
One party claims the terms of service were different when they signed. The other party's website has been updated since. Courts have found that Wayback Machine screenshots alone may not satisfy authentication requirements.
With BitProof: The terms page was archived at signing. The bundle includes three independent captures, screenshot, HTML source, and PDF rendering, with a composite hash anchored to Bitcoin. This can materially strengthen later authentication arguments with verifiable cryptographic records.
Intellectual Property
An inventor needs to prove when a design existed
A patent dispute turns on priority, who had the idea first. Lab notebooks and email timestamps are controlled by the parties involved and can be questioned.
With BitProof: The inventor timestamped their design documents at the time of creation. The proof is anchored to Bitcoin's blockchain, which no individual or organization controls. The timestamp is based on cryptographic verification, not testimony.
Accountability
A public figure deletes a social media post
A politician posts a controversial statement, then deletes it. Screenshots circulate but are dismissed as potentially fabricated.
With BitProof: Someone archived the page while the post was live. The archive bundle, containing the full page capture, is anchored to a Bitcoin block mined at that time. Deletion does not erase proof.
Eyewitness
A bystander captures a breaking event on a phone
A photo of a crash or fire is challenged online as edited or AI-generated. EXIF timestamps are easy to alter and screenshots alone are easy to dispute.
With BitProof: The witness timestamps the original phone image immediately. Later, anyone can verify the same file hash against Bitcoin anchoring and confirm the file has not been altered since the captured proof time.
Mobile journalism integrity workflow
Designed for fast field reporting when context can disappear quickly.
Field Workflow
Capture now, verify later, publish with stronger evidence
BitProof now supports direct mobile camera or photo timestamping plus one-tap archive entry for shared URLs.
Capture the image or video frame on your phone.
Timestamp immediately with Use Camera / Photo or share a URL into archive flow.
Keep the original file and .bitproof bundle for independent verification.
Result: You can later demonstrate that the evidence file existed by a specific anchored time and has not changed since.
Screenshot vs. BitProof archive
A screenshot is a picture. A BitProof archive is evidence.
Screenshot
Can be fabricated or edited
No proof of when it was taken
No underlying source data
Relies on trust in the person who took it
Often challenged in disputes
BitProof Archive
Screenshot + HTML + PDF captured independently
Timestamp anchored to a specific Bitcoin block
Full source code preserved
Verifiable without trusting anyone
Cryptographic chain of proof
How it works
1
Hash locally, send nothing
For files, your content is hashed in the browser using SHA-256. Only the 64-character hash reaches our server. For web archives, our server loads the URL and captures three independent representations.
2
Anchor to Bitcoin
The hash is submitted to OpenTimestamps, which aggregates hashes into a Merkle tree and anchors the root to a Bitcoin transaction. One transaction can cover thousands of timestamps.
3
Download your proof
You receive a self-contained .bitproof bundle. It includes everything needed for verification. We don't store copies. If we disappear, your proof still works.
4
Verify independently
After 1-2 hours, the proof confirms on Bitcoin. Anyone can verify it using standard OpenTimestamps tools and any Bitcoin node. No accounts, no logins, no dependencies.
What BitProof does not prove
Honesty about limitations is part of the design.
BitProof proves that specific content existed in a specific form at a specific time. It does not prove who created it, whether it is true, or who owns it. A timestamped document could contain false information; the proof only covers existence and integrity, not accuracy or authorship.
Optional authorship signatures prove control of a specific cryptographic key. They do not prove legal identity.
Try it now
Timestamp a file or archive a web page. It takes seconds.