Timestamp a demo before you send it anywhere. ProofLedger writes a fingerprint of your track to a public blockchain, so the date it existed is fixed by the network instead of by a file property anyone can change. Your audio never leaves your computer.
A demo goes to a collaborator, a manager, a sync agent, a producer you met once. What you keep is a date that lives in places you do not control.
The created and modified dates on an audio file belong to the filesystem, not to the music. Copy the file to another drive, bounce a new version, or open the session on a different machine, and they move. They can also simply be set to whatever someone wants.
Your email shows the day you sent a file to someone. It says nothing about the day you made it, and it sits inside an account you can lose access to, that you cannot show to a third party without handing over everything around it.
The normal way to show you had something early is to send the file again, to someone else, and hope they keep it. That means giving an unreleased recording to another party just to build a paper trail.
Drop in a bounce, a voice memo, a session file, a set of stems. Anything that is a file.
The file is read on your own machine and reduced to a SHA-256 fingerprint: 64 characters that change completely if a single byte of the recording changes.
That fingerprint is written into a transaction on the Polygon blockchain. The timestamp comes from the network, which means it is not a date we typed into a database we own.
A signed certificate and a public verification page. Anyone you send the link to can confirm the fingerprint and the date themselves, without an account, and without you sending them the track.
The fingerprinting runs inside your browser through the Web Crypto API, crypto.subtle.digest. The bytes of the recording are read into local memory and are never uploaded. What is sent to us is the fingerprint, plus the file name, size and type so you can recognise the proof later.
A SHA-256 fingerprint is one way. It cannot be turned back into the track. This is how the upload page is built, not a policy we are promising to keep.
Worth being clear before you rely on it for anything.
Timestamping is the free tier. There is no cap on how many tracks you put through it.
Unlimited Polygon proofs are subject to fair-use limits that keep the service up. Certificates are a human-readable view; the blockchain anchor and the public verification page are the authoritative record.
It takes about a minute, the track stays where it is, and the date stops depending on anyone remembering anything.
