PROXAE

Use case

Protect source code

To protect source code without publishing it, you need to prove it existed at a given date. Proxae timestamps the SHA-256 hash of your code in the Bitcoin blockchain — your code stays on your machine.

Developing an algorithm, software, or API? Timestamp your source code to prove you wrote it on a given date — without making it public.

Certify my code →

The problem

A Git commit proves local history, but it can be rewritten. A private repo has no external evidential value. To prove to a third party that your code existed on a given date, you need an independent timestamp.

Real-world examples

▸

A startup certifies its proprietary algorithm before pitching to investors — proof of priority if the idea is copied.

▸

A freelance developer archives and certifies each deliverable before handing it to the client — traceability and protection.

▸

An open source project timestamps each release via the Proxae API in its CI/CD pipeline — verifiable and immutable history.

How to do it

1

Archive your code

Create a ZIP archive of your project or select a key file. The SHA-256 fingerprint is computed in your browser.

2

Blockchain timestamp

The fingerprint is anchored in a Bitcoin block. No code is transmitted — only the 64-character hash.

3

Prior art proof

In case of dispute, you can demonstrate your code existed before a given date by re-hashing the archive and verifying the OpenTimestamps proof.

Your code has value. Certify it before sharing — it's free and instant.

Certify my code

Proxae vs other code protections

Proxae Software escrow Git commit
Cost ✓ Free $400+ Free
Speed ✓ Instant Weeks Instant
Privacy ✓ Full (local hash) Code handed over Local
Permanence ✓ Permanent (Bitcoin) Variable Rewritable

Ideal for

  • ✦ Startups — protect your technical intellectual property
  • ✦ Freelancers — prove authorship of your work
  • ✦ Open source — timestamp before publishing
  • ✦ CI/CD integration — automate with the Proxae API

Frequently asked questions

Is my code sent to Proxae?
No. Only the SHA-256 hash is transmitted. Your source code stays on your machine.
Can I automate the process?
Yes. The Proxae API lets you timestamp programmatically. Integrate it into your CI/CD pipeline to certify each release.
Does this replace a software patent?
No. Proxae proves existence, not ownership. But it is a very useful complementary piece of evidence, especially when a patent is not applicable.
Isn't a Git commit enough as proof?
A Git commit proves local history, but it can be rewritten (rebase, amend). It has no external probative value. Bitcoin timestamping is immutable and verifiable by any independent third party.
How to integrate Proxae in a CI/CD pipeline?
The Proxae API allows programmatic timestamping. Compute the SHA-256 of your release archive and send it via the API. Each build is automatically certified.
Certify my code

Local hash, Bitcoin proof, total privacy.