Overview · For partners and investors
The ID and trust layer for music.
Suede AI IP Registry gives every finished work one public ID: an exact-file fingerprint plus a wallet-signed, timestamped creator claim on Base and Avalanche mainnet. Distribution, streaming platforms, the musician, and every derivative can point to it. Anyone can verify it without asking Suede.
2
Public mainnets · Base and Avalanche
17
Works on record · read live from chain
~1¢
Network gas per registration
0
Permissions needed to check a record
- 01Distribution
- 02Streaming platforms
- 03Musician
- 04Derivatives
I · The problem
Music has lists.
It lacks a shared record.
Every party keeps its own list.
Distributors, streaming platforms, collaborators, and catalogs each hold their own IDs and credits. None of them points back to one signed record of who made the work.
Claims live in private databases.
To learn who claimed a work and when, you usually have to ask whoever holds the database, then trust the answer. No one outside it can check.
Derivatives outrun the credits.
Remixes, covers, samples, and AI-assisted versions multiply faster than liner notes can follow. Who made this, and what did it come from, is now the question every party gets stuck on.
II · The layer
Four parties.
One public ID.
The registry sits underneath the chain a song already travels. Each party asks a different question, and each gets its answer from the same record, fixed at the source by the person who made the work.
The chain of record
Four parties · one public ID
01 · Distribution
The release goes out.
Asks
Which master is this, and who stands behind it?
The registry gives it
A fixed ID for the master before release day. Keep the fingerprint and transaction link with the release files, and the version that ships can be checked against a dated public claim.
- Live today
- Register the master and keep its ID with the release records. Suede AI Distro is sold separately ($7.99/mo), coordinates delivery through supported partners (coverage and eligibility vary), and does not create a registry record.
- Next · not live yet
- Release identifiers (ISRC, UPC) written against the ID, and a Distro handoff that files the record at release.
Anchor live02 · Streaming platforms
Listeners press play.
Asks
Who made this, and when did they claim it?
The registry gives it
A lookup anyone can run without asking Suede: creator wallet, contributors, timestamp, and lineage, readable on two public blockchains.
- Live today
- Public record pages, the browsable register, and block-explorer checks. No platform integration is required to read a record.
- Next · not live yet
- A lookup built for platforms and catalog teams.
- Limit
- The fingerprint matches exact files. A re-encoded stream will not hash-match, so platforms resolve a work by its record, not by listening to it.
Lookup live03 · Musician
The work is claimed.
Asks
Who made it, who worked on it, and what did they declare?
The registry gives it
A wallet-signed creator claim listing the contributors and a rights declaration, timestamped in about two minutes for about a cent.
- Live today
- Registration on Base and Avalanche mainnet. Signing up creates a wallet, so no crypto knowledge is needed.
Live04 · Derivatives
The work travels.
Asks
What did this remix, cover, sample, or AI-assisted version come from?
The registry gives it
Each derivative is registered as its own work, then linked to its parent on-chain, so where it came from is part of its record.
- Live today
- Parent-to-child links written on-chain from the registry dashboard.
- Next · not live yet
- Lineage shown on every public record page.
- Limit
- A link records the relationship. It is not a clearance to use the parent.
Live
The registry record
One ID under all four.
Specimen values
- Fingerprint
- 0x7f3a91c0…42d7f83aSHA-256 of the exact file
- Certificate
- № 13 · ERC-721The public token for the work
- IP account
- 0x3b19e5a2…c07d41f8The work’s own on-chain address
- Signed claim
- 0x8d4c1f72…6ab9e2a1Creator wallet, contributors, declaration
- Timestamp
- block 31,442,205Set by the chain, not typed in
- Lineage
- parent → № 13Where a derivative came from
Anyone can verify it, and Suede cannot quietly edit or backdate it. It is provenance evidence, not a copyright registration and not proof of legal ownership.
III · Proof it is live
Deployed, public,
and checkable today.
The same registry contracts run on two public blockchains. Every address below is a live production deployment. Click through to read the code and every transaction.
- Registry
- 0x264eFed8…c27a3A
- Certificates (ERC-721)
- 0xB957C84B…805FFb
- Registry
- 0xAC2bf87F…B1121C
- Certificates (ERC-721)
- 0x6436c232…9d97c1
Musicians never have to touch this layer: signing up creates a wallet, and a registration costs about a cent in network gas. The records themselves are browsable in the public register.
IV · Verification
Anyone can check a record
in three steps.
Trust comes from the fact that a distributor, a platform, a lawyer, or an AI agent can confirm a record on its own.
- 1.
Find the record
Search the public register by title, or open ip.suedeai.ai/ip/ followed by the fingerprint.
- 2.
Match the file
Run SHA-256 on your copy, for example shasum -a 256 master.wav. If the result equals the record’s fingerprint, it is the exact file that was registered.
- 3.
Check the chain
Open the record’s explorer links on BaseScan or Snowtrace to see the signing wallet, the transaction, and its block time. None of this needs Suede’s cooperation.
V · Status
What is live,
and what comes next.
| Capability | Status | Detail |
|---|---|---|
| One public ID per exact fileSHA-256 fingerprint, certificate token, and IP account. | Live | SHA-256 fingerprint, certificate token, and IP account. |
| Wallet-signed creator claimWith contributors and a rights declaration. | Live | With contributors and a rights declaration. |
| Timestamped records on two mainnetsBase and Avalanche, identical contracts. | Live | Base and Avalanche, identical contracts. |
| Derivative lineageParent-to-child links written on-chain. | Live | Parent-to-child links written on-chain. |
| Public register and record pagesReadable by anyone, no account needed. | Live | Readable by anyone, no account needed. |
| Suede AI Distro$7.99/mo release service through supported partners; coverage and eligibility vary. It does not create a registry record. | Separate product | $7.99/mo release service through supported partners; coverage and eligibility vary. It does not create a registry record. |
| Release identifiers on the recordISRC and UPC written against the ID. | Next | ISRC and UPC written against the ID. |
| Distro handoff at releaseA release that files its registry record as it ships. | Next | A release that files its registry record as it ships. |
| Platform lookupA lookup built for streaming platforms and catalog teams. | Next | A lookup built for streaming platforms and catalog teams. |
| Lineage on public record pagesParents and derivatives shown on every record. | Next | Parents and derivatives shown on every record. |
Next items are plans, not commitments or dates. Nothing marked Next is available today.
The boundaries
What a record is not.
Not a copyright registration.
For statutory benefits in the US, register with the Copyright Office. A record is dated provenance evidence.
Not proof of legal ownership.
It shows what a wallet claimed and when. Suede does not adjudicate who owns a work.
Not a clearance.
A derivative link records the relationship. Permission to use the parent comes from the agreement, not the registry.
Not audio recognition.
The fingerprint identifies exact bytes. A re-encoded or edited file produces a different fingerprint.
One work. One ID.
Checkable by anyone.
Put a work on the record, look one up, or talk with Suede about building on the registry.