Use case
Blockchain Timestamps for Musicians
Anchor unreleased tracks before you share them. Prove you wrote it first. Verifiable in seconds, permanent on the blockchain.
The problem musicians actually face
You write a track. You send a demo to a producer, a label rep, a friend, or upload it to a private SoundCloud link. Months later you hear something that sounds suspiciously close — same melody, similar hook, your structure. The question is always the same: can you prove you had it first?
Email timestamps can be faked or manipulated. DAW project file dates can be altered. Cloud storage timestamps reflect when the file was uploaded, not when it was created. The recording itself has no embedded evidence of when you made it. Without a tamper-evident timestamp anchored to an independent source, the burden of proof falls on you, and you usually can’t meet it.
What blockchain anchoring does for a track
ProofAnchor takes the SHA-256 hash of your audio file and writes it to the Polygon blockchain. The audio never leaves your device — only the 64-character fingerprint is transmitted. The on-chain timestamp is a permanent, public record that the exact file existed at that moment. Anyone with the file can verify the timestamp against the blockchain without trusting ProofAnchor.
If the track is altered later — re-mastered, re-arranged, transcribed differently — the hash changes and the new file no longer matches the on-chain record. The original timestamped version is locked.
How musicians use it in practice
Anchor demos before pitching
Before sending a demo to a label, manager, sync agency, or producer, anchor the file. The timestamp predates any conversation. If the demo gets passed around, modified, or leaked, the original anchor is your proof of authorship and date.
Anchor stems before collaboration sessions
When you send stems to a remixer, co-writer, or producer, anchor them first. The timestamp documents exactly what you contributed and when. Co-writing disputes get cleaner: each party can show what they brought into the session.
Anchor masters before distribution
Before uploading to DistroKid, TuneCore, or any DSP aggregator, anchor the master. Aggregators and DSPs occasionally have data issues, claim issues, or release-date disputes. The anchor is independent of the platform.
Anchor sketches and works-in-progress
A voice memo of a chorus idea. A piano sketch. A guitar riff captured on your phone. Anchor anything you might develop into a finished song. The early anchor establishes when the core idea came to you.
Anchor before social media drops
Before posting a teaser on Instagram, TikTok, or X, anchor the file. Platforms strip metadata and compress audio. The anchor preserves proof of the unaltered original predating the public post.
AI training and audio
Generative audio models (Suno, Udio, MusicGen, and others) train on large datasets of recorded music. If your unreleased tracks were ingested into a training set without permission, the question in any dispute is: when did your track exist? A blockchain anchor predating the model’s training cutoff is the cleanest answer available.
This applies to demos that were leaked, private SoundCloud uploads that were scraped, and files shared on services that may have included audio in training datasets. Anchoring before any share establishes the timeline.
Does this replace music copyright registration?
No. In the US, music copyright exists automatically when a work is fixed (recorded or notated). Registration with the Copyright Office unlocks statutory damages and attorney’s fees in litigation. A blockchain timestamp doesn’t give you those legal weapons.
What it gives you is verifiable proof of when a specific recording existed — which can be useful before you ever decide whether something is worth registering, in disputes that don’t go to federal court, and for the 95% of demos and sketches you’ll never register.
Pricing
Free tier: 5 lifetime anchors. Pro: $9.99/month for 50 anchors. Business: $49.99/month for 500 anchors plus API access for automated DAW workflows. See pricing.