DistroKid Takedowns Hit Real Artists | Elacity
UMG sued DistroKid, and real indie songs vanished with the slop. The deeper flaw: your rights record, royalties, and proof of authorship lived in someone else's database.
DistroKid Takedowns Hit Real Artists. The Rights Record Was Never Theirs.
If you release music through a distributor, your catalog, your royalty balance, and your proof of authorship all sit in one company's database. The DistroKid takedowns of the past month showed what that costs you: a claim lands on the distributor, and your songs can vanish from streaming before anyone asks you a question.
This is not a story with an obvious villain. Universal Music Group sued DistroKid on September 15 in Delaware federal court, alleging the distributor floods streaming services with undisclosed AI tracks and copies of UMG recordings. UMG's complaint claims nearly 12 million tracks reached one unnamed service in six months, more than half of everything that service received.
That is a genuine problem for every working musician competing with machine-made filler for the same royalty pool. The trouble is what happened next.
The Failure of DistroKid Takedowns: The Proof Lived in the Wrong Place
DistroKid confirmed it removed a very small number of recordings in response to UMG's claims, while saying it strongly disputes the allegations. Artists describe a messier picture.
- Musician McGwire reported six songs pulled; one notice cited an uncleared sample from a record released two years after his own track.
- Nashville songwriter Josh Sahunta found his 2022 album gone and, Law Commentary reported, received a copyright strike he says froze his royalty payments.
- Many notices named only UMG as the claimant and offered no visible way to dispute the removal.
The formal remedy is a counter-notice, after which DistroKid says it must wait 10 business days before reinstating, and streaming services may still decline. Weeks of silence on a release are momentum you do not get back.
Look at the structure rather than the parties. The rights record, the payout ledger, and the delivery pipe are one company's account system. When that company is sued, the cheapest move is to pull broadly and sort it out later, and your income waits in the queue.
The same shape shows up in the songwriter rate proceeding where proposals were filed on October 5, deciding what a stream pays for 2028 through 2032. Whether the question is your rate or your right to stay listed, it gets settled in rooms where your own records are not the source of truth.
The Paradigm Shift: Ownership That Doesn't Route Through a Support Ticket
The people who create the value should own it. That is the entire reason Elacity exists. (Sasha Mitchell, Founder)
Elacity starts there. Through Elacity dDRM, a musician wraps a track, a stem pack, or an album into a Wealth Capsule: an encrypted, programmable good with rights and royalty terms written in and settled on-chain. Beneath it runs ElastOS, the open-source runtime that keeps the whole thing on a computer you own.
That changes three specific things about a day like the one these artists had.
1. Authorship is a dated record you signed, not a row in their database
Minting a Wealth Capsule writes to the chain that your key sealed this work at this moment. A dispute like McGwire's, where the allegedly sampled record came out later, turns into a lookup anyone can check instead of a ticket someone has to answer.
Be clear about the limit: a record minted today cannot prove a 2022 album came first. It does not decide copyright either. What it gives every release from here forward is a receipt that no distributor can lose, edit, or hold.
2. The royalty rule sits at the key, not in a payout ledger
Every unlock of a Wealth Capsule passes a rights gate. The key is split across an owned 2-of-3 quorum of independent machines, and each one re-checks your on-chain rights before releasing its share, so the terms you wrote travel with every use.
Rights and payment settle on the same chain the gate reads. Your terms are not parked in a middleman's account, waiting for a strike to freeze them. Not a platform you rent; a market you own.
3. Your master stays on a computer you own
ElastOS treats your own machine, through Personal Cloud Compute, as the source of truth, with the cloud as a swappable guest. Content stays encrypted everywhere except the sealed moment of use, so a listener gets the stream and never the key.
A delisting can close a storefront. It cannot reach into your machine and take the original.
What This Does Not Fix
An infringing track is still infringing once it is sealed. Elacity does not judge copyright fights, and courts can order a delisting on any storefront, ours included. The narrower claim is about blast radius: a dispute should land on the disputed asset with evidence attached, not freeze an artist's whole catalog while support works a queue.
Some of this is still being built. The consumer Create-and-sell portal on the Elacity Exchange is in progress, and ElastOS runs fullest on Linux today. The sealing, the split-key quorum, and the on-chain rights check already work.
For the full mechanics, our explainer on who holds the key to what you bought walks the quorum step by step, and why a royalty you own beats a payout you are permitted covers the platform side. More lives in the Creator Economy hub.
Distributors will keep getting sued, and some of those suits will be right. Make sure the next one hits a storefront, not the only copy of your proof. Get ElastOS