IP Registry and rights records

What it is

The Suede IP Registry, at ip.suedeai.ai, is where creator claims get filed. Its tagline is literal: your music, on the record. You upload a file, the registry computes an exact-file fingerprint, records a timestamp, and stores the claim with its contributors. The result is a durable, inspectable record that this work existed in this form at this moment and that you claimed it.

What a record contains

• Fingerprint: a cryptographic hash of the exact file. Change one sample and the fingerprint changes, which is what makes it useful: it binds the claim to a specific artifact rather than a vague description.
• Timestamp: when the claim was filed. Order matters in ownership disputes, and a timestamp that predates public release is strong evidence of priority.
• Contributors: who made it, with roles and splits. This doubles as a split sheet, captured at the moment memories are fresh and stakes are low.
• Permissions: machine-readable statements of what is allowed, including an explicit position on AI training rather than silence.
• Routing: where payments go when the work earns, applied automatically to transactions that flow through Suede.

What registration is, honestly

A Suede registration is evidence and infrastructure. It gives you a timestamped, fingerprinted claim you can point to, permissions machines can read, and payment routing that works today.

It is not a government copyright registration. In jurisdictions like the United States, statutory registration carries specific legal advantages (such as eligibility for statutory damages), and if a work matters commercially you should do both. Suede's view is that these layers stack: the registry gives you day-one evidence and machine-readable rights for the 99% of interactions that never reach a courtroom, and formal registration covers the 1% that might.

A fingerprint also proves the file existed, not that no earlier version existed somewhere else. Registries record claims; they do not adjudicate them. Honest documentation, kept early and consistently, is what makes your claim the strong one.

Likeness and voice

The registry model extends beyond finished works. Suede supports provenance records for likeness and voice reference files, the material that defines what you look and sound like, so that permissions about cloning and imitation can be stated in machine-readable form instead of asserted after the fact. See the AI voice protection and AI likeness protection pages on this site for the current state of those protections.

Multi-chain registries

Suede anchors registry infrastructure on public chains, with Base as the primary settlement environment for payments, and registry surfaces for other ecosystems (Solana, Avalanche) linked from the Explore menu. Onchain anchoring is a durability choice: a public, append-only record is hard to quietly edit, including by us.

How to use it well

1. Register early and often. Demos, stems, and drafts all carry timestamps. More records means a richer evidentiary trail.
2. Fill in contributors at filing time. Retroactive split sheets are where friendships go to die.
3. State your AI position explicitly. Silence is currently treated as permission by too many crawlers. A machine-readable no (or a priced yes) is stronger than an unstated preference.
4. Keep your originals. The registry holds the claim; your archive of session files and source material is what proves the human authorship behind it.