Spotify Tracks Every Stream. The Music Itself Has No Computable Identity.

Spotify's royalty accounting, creator tools, and discovery algorithms serve millions of artists and billions of listeners. The gap described here is not about the platform's tracking capabilities within its own ecosystem. It is about what the content itself can prove about its own identity.

ISRCs are database identifiers, not content identity

Every track on Spotify has an International Standard Recording Code. The ISRC identifies a specific recording in databases. But the ISRC is a registry entry, not a property of the audio. The same recording uploaded with a different ISRC is treated as a different track. A different recording uploaded with the same ISRC is treated as the same track. The identifier is disconnected from the content.

This creates well-known problems. The same recording may appear under multiple ISRCs due to re-releases, remastering, or distribution errors. Different recordings may share an ISRC due to metadata mistakes. The registry does not verify that the content matches the identifier.

Audio fingerprinting is detection, not identity

Spotify and the broader music industry use audio fingerprinting to identify recordings. These systems create condensed representations of audio that can be matched against a database. They are effective for identifying exact or near-exact copies.

But audio fingerprinting is a search mechanism, not an identity system. It requires a database of known fingerprints to match against. A recording not in the database cannot be identified. A derivative work that differs sufficiently from the source will not match. The fingerprint does not travel with the content. It exists only in the matching database.

What content anchoring provides

Content anchoring derives identity from the content's own structural properties. For audio, this means entropy distribution across frequency bands, temporal structure signatures, and spectral patterns. The identity is computable from the audio itself, without reference to a database.

With content anchoring, a remix would carry structural lineage linking it to its source recordings through shared structural properties. A sample used in a new composition would be structurally identifiable within the composite work. Re-uploads and re-encodes would retain identity because the structural properties survive standard audio transformations.

Rights attribution would shift from database lookups to structural computation. The content itself would prove its lineage, enabling rights resolution that works across platforms rather than within a single platform's database.

The remaining gap

Spotify tracks every stream within its platform. The remaining gap is in content identity: whether music can prove what it is from its own structural properties, enabling rights resolution that works across platforms, survives transformations, and does not depend on database identifiers.