An algorithm or feature can be claimed by anyone
First scenario: a freelance developer delivers a feature to a client, who then claims to be the intellectual author and refuses to pay. Second scenario: an independent developer creates an original algorithm, a competitor releases the same one a few months later and disputes authorship. In both cases, a Git commit or email is not enough — they can be backdated or contested. Only a timestamped proof from a trusted third-party authority is technically unassailable.
A certified fingerprint of your code, outside your Git repository
I'm finalizing a stable version of my code or a technical deliverable.
I generate a timestamped proof of my project's ZIP file before delivery or publication.
I can prove this exact version existed at this date, independently of Git.
The code never leaves my device. Only the SHA-256 fingerprint is transmitted.
Accepted formats: ZIP, TAR.GZ, JS, PY, SQL, compiled binaries — all formats
3 steps, 30 seconds
- Drop your file: Project ZIP, source file, compiled binary…
- Automatic certification: SHA-256 hash computed in the browser + RFC 3161 timestamp via FreeTSA
- Download your Proof Pack: Readable PDF certificate + .tsr token verifiable by any RFC 3161 compatible tool
Why not just use Git?
Git is a versioning tool, not an external proof tool.
| Criterion | Git Commit | GitHub timestamp | ProofStamper |
|---|---|---|---|
| Backdatable | Yes (git commit --date) | No | No (external TSA) |
| Platform dependent | No | Yes (GitHub) | No |
| Code confidentiality | Local | Hosted | 100% local |
| Independently verifiable | No | No | Yes (RFC 3161) |
| External technical proof | No | No | Yes ✓ |
Protect every key step of your development
- Client delivery — Prove the exact date a technical deliverable was handed over.
- Software patent filing — Document the anteriority of your invention before any publication.
- Proprietary algorithm — Freeze a version of your algorithm before sharing or collaboration.
- Pre-open source version — Timestamp your code before publishing it under an open license.
- Compliance audit — Prove the exact state of a system at a specific date.
- Non-regression proof — Certify that a version passed tests at a given date.
Frequently asked questions
- Isn't a Git commit enough as proof?
- A Git commit can be backdated with git commit --date. It's an internal versioning tool, not independent proof. ProofStamper uses a third-party timestamp authority (RFC 3161) that certifies the date in an incontestable manner.
- Is my source code sent to your servers?
- No, never. All processing happens locally in your browser. Only the cryptographic fingerprint (SHA-256) — a unique identifier that cannot reconstruct your code — is sent to obtain the timestamp.
- Can I timestamp an entire project in a single ZIP file?
- Yes. Compress your project as ZIP or TAR.GZ and drop it. The SHA-256 fingerprint covers the entire content. If a single byte changes, the fingerprint will be different.
- Is this proof usable in a commercial litigation context?
- Yes. The RFC 3161 certificate is a recognized technical proof of anteriority. Combined with a bailiff's report, it constitutes strong evidence to establish the existence date of a file.