GUIDE
How to certify properly
Everything you need to know to make your certification solid and verifiable.
Why a file rather than text?
Proxae certifies the SHA-256 fingerprint of your content. This fingerprint is calculated locally in your browser and is extremely sensitive: an extra space, a different accented character, or a simple line break completely changes the fingerprint. With a PDF file, the file itself is the reference — you just need to keep it as-is.
How to create a PDF from any document?
Word / LibreOffice
File → Export as PDF (or Save as → PDF)
Google Docs
File → Download → PDF Document (.pdf)
Pages (Mac)
File → Export to → PDF
Any application
Print → choose "Save as PDF" as the printer
How to store your file safely?
The Proxae proof anchors your fingerprint in Bitcoin — but you must keep two files to prove it later: the original file (never rename or modify it) and the .ots file downloaded from your proof page. Without the .ots, you have no way to prove the Bitcoin anchoring independently from Proxae.
Tip: create a dedicated "Proxae Certifications" folder on your cloud (Google Drive, iCloud, Dropbox…) and store, for each certification, the original file AND its .ots side by side.
Pro users: download the .zip bundle from your proof page. It contains all files needed for independent verification — keep it alongside your original file.
Pro users: the eIDAS certification bundle
In addition to the Bitcoin anchor (.ots), every Pro proof includes a qualified RFC 3161 timestamp issued by Sectigo — a Qualified Trust Service Provider (QTSP) accredited under the European eIDAS regulation. This dual anchoring gives your proof maximum evidential weight before European courts.
The ZIP bundle downloadable from your proof page contains:
- ◆ proof.ots — Bitcoin anchor (OpenTimestamps)
- ◆ proof.tsr — qualified eIDAS certificate (Sectigo TSA)
- ◆ proof.tsq — original timestamp request
- ◆ sectigo-chain.pem — Sectigo certificate chain
- ◆ metadata.json — SHA-256 hash, dates and ready-to-run openssl commands
openssl verification with the bundle:
openssl ts -verify -in proof.tsr -queryfile proof.tsq -CAfile sectigo-chain.pem
The Proxae /verify page also accepts the .tsr file directly in your browser.
How to verify a proof in the future?
Verification is possible even if Proxae no longer exists. You simply need to:
- 01 Find your original file (unmodified)
- 02 Calculate its SHA-256 fingerprint (via Proxae or any standard tool)
- 03 Compare it with the fingerprint recorded in your Bitcoin proof
- 04 Verify the Bitcoin anchor via the .ots file downloaded from your proof
Pro users: also verify the eIDAS certificate (.tsr) on the /verify page or using the openssl command provided in metadata.json.
What if I lost my original file?
Let's be honest: the Proxae proof still exists in the Bitcoin blockchain and no one can erase it. But without the original file, you can no longer demonstrate that *your* content matches this fingerprint. The certification proves that a fingerprint existed at a given date — the match with your content is up to you. That's why storage is the most critical part of the process.
