Introducing MilliHash: Prove What You Had, When You Had It
Updated: Oct 30

Say you wrote a song last spring, and today someone releases something suspiciously similar. Or you signed a contract, and the other side now claims the terms were different. Or a photo you took is being called a fake. In each case, the question is the same: can you prove what you had, and when you had it?
Most of the ways people try to prove this are weak. The date on a file can be changed in a few clicks. A cloud drive's records belong to a company you'd have to subpoena. Emailing yourself a copy shows little more than that you sent an email.
MilliHash gives you a record that holds up. You register a file, and MilliHash gets an independent, tamper-proof confirmation of exactly what it was and exactly when you had it. Anyone can check that record later, without needing to trust you, or even MilliHash.
How It Works
Every file gets a fingerprint. When you register a file, MilliHash computes a short code that's unique to its exact contents, a kind of digital fingerprint. Change a single letter or pixel and the fingerprint changes completely. You can't work backward from the fingerprint to the file, so it reveals nothing about what's inside.
The fingerprint is stamped by a neutral witness. MilliHash sends the fingerprint to an independent timestamp authority, which signs it with the exact date and time. This is the same kind of service businesses and governments use to time-stamp electronic signatures.
Then it's written into the Bitcoin blockchain. Within a few hours, the fingerprint is also recorded on Bitcoin, a public ledger copied across thousands of computers worldwide. Once it's there, no one, including MilliHash, can change or delete it.
To prove your claim later, you show the original file. Anyone can compute its fingerprint, find the matching record, and see when it was registered.
A few more things worth knowing:
MilliHash never keeps your file. Only the fingerprint is stored. You can even compute the fingerprint on your own device, so the file never leaves it.
You can track versions. Group drafts of the same work into a project. Each version is linked to the one before it, building a dated history of how the work developed.
Checking a record is free and open. Anyone can verify a registration or certificate without an account.
Your proof outlives MilliHash. You can download the Bitcoin proof file and check it independently, even if MilliHash someday shuts down.
One honest limit: a registration proves that you had an exact file at a specific time. It doesn't prove you created it. A history of drafts can support that claim, but it isn't proof on its own.
Trying It
The simplest way to start is the MilliHash web app. Drop in a file, and it tells you whether that exact file has been registered, and when. With a subscription, you can register your own files and download a certificate for each one.
For Developers
MilliHash is also an API, so you can build it into your own apps. Verification needs no sign-up. MilliHash registered a sample text you can check:
# Fetch the sample text MilliHash registered
curl https://api.millihash.com/sample
# Verify it - no API key needed
curl -X POST https://api.millihash.com/verify \
-H "Content-Type: application/json" \
-d '{"contentType": "text", "text": "<sample text from above>"}'To register your own assets:
Subscribe on RapidAPI. The free BASIC plan includes 25 registrations a month, project lineage included.
Register an asset. Send a file, text, or your own SHA-256 hash to POST /registrations. You get a TSA timestamp and a certificate back immediately.
Check the Bitcoin anchor. Anchoring happens in the background, typically within a few hours. Check progress with GET /anchors/{id}, then download the anchored certificate.
Track versions. Create a project with POST /projects, then append each new draft with POST /projects/{id}/versions.
curl -X POST https://millihash.p.rapidapi.com/registrations \
-H "X-RapidAPI-Key: YOUR_KEY" \
-H "X-RapidAPI-Host: millihash.p.rapidapi.com" \
-F "submissionMode=server-computed" \
-F "label=Chapter 1 draft" \
-F "file=@chapter1.docx"The API reference covers every endpoint in detail.
Possible Uses
Creative Work
Register each demo, draft, or design iteration as a version in a project. The result is a dated record of how the work developed.
Contracts and Legal Documents
Timestamp every contract revision so there's an independent record of which version existed when, and in what order.
Media Authenticity
Register original photos and videos as soon as they're captured. If a manipulated copy surfaces, you can prove the original came first.
Research and Data
Timestamp datasets and findings before publication to establish priority and show your data wasn't altered after the fact.
What's Next
Planned work includes:
JavaScript client SDK — hash locally and register in a single call.
Microsoft Word add-in — timestamp contract and manuscript versions without leaving the editor.
Normalized-text verification — match text even when whitespace or formatting has changed.
Feedback
Feedback will shape what gets built next. I'd like to hear:
Which tools you'd want MilliHash built into
What kinds of assets you need to protect, and how large they are
Anything confusing in the docs or the certificates
Use cases I haven't thought of
Reach out through the contact page or open an issue on GitHub.