Source code ownership disputes are common: a founder leaves, a contractor claims their work predates the contract, a former employer says a side project was built on company time. Commit histories help, but they can be rewritten and their dates come from the developer’s own machine.
TimeBinder lets developers and software companies record independent proof of what code existed at a point in time, on the Bitcoin blockchain, without uploading a line of it.
What developers TimeBind
- A zip of the repository at each release or milestone
- A text export of commit hashes (for example
git logoutput) to anchor the whole history - Pre-existing code before you start a contract or join a company
- Specifications, architecture documents and design files
- Licences and contributor agreements
How it works
- Choose up to 10 files. Any file type and size works.
- Your browser calculates each file’s SHA-256 fingerprint. The files themselves are never uploaded, so unreleased work stays on your device.
- Choose Pooled (batched with other TimeBinds, usually recorded within about 24–36 hours) or ASAP (your own Bitcoin transaction, broadcast straight away and verifiable without TimeBinder).
- Download your Proof of Time Certificate, a PDF with a QR code and the Bitcoin transaction ID.
- Keep your original files unchanged. Anyone you share access with can later re-check a file against the record in their browser.
Check a fingerprint yourself
Want to see the SHA-256 fingerprint of any file before you TimeBind it? Use our free SHA-256 File Hash Checker. It runs entirely in your browser.
What a TimeBind proves, and what it does not. A TimeBind proves that your file existed no later than the time it was recorded on the Bitcoin blockchain, and that it has not changed since. It does not prove who created the file, that its contents are true, or that a court will admit it. It is independent evidence of timing to use alongside your other records, and it is not legal advice.
Frequently asked questions
Aren’t Git commit dates enough?
Git records the dates that the committer’s machine supplies, and history can be rewritten. A TimeBind of a release archive or commit list anchors the timing to the Bitcoin blockchain, outside anyone’s repository.
Is my source code uploaded?
No. Your browser calculates a fingerprint of each file. The code never leaves your machine.
How often should I TimeBind my code?
A practical rhythm is each tagged release or major milestone, plus whenever code changes hands: before a contract starts, when a contractor delivers, and before investor due diligence. Zip the source or release artefacts and TimeBind them in the web app.
Does it prove I own the code?
No. It proves the files existed by a set time and are unchanged. Ownership depends on your contracts and employment terms; a TimeBind gives those records an independent timeline.
Start free: your first Pooled TimeBind each month costs nothing.