Every Suede work, every license, every split — written to Base.
The Suede registry lives on Base mainnet (chain ID 8453). Every registered work, every license, every split mutation hits the chain and stays there. This page is the live mirror — the source of truth that powers verification, royalty routing, and marketplace listings.
Works registered
5,200+and counting
Active licenses
2,100currently enforceable
Splits routed
$418Klast 12mo
Block
latestrefreshed live
Chain
Base · 8453L2 settlement
Bridge
LayerZerocross-chain in
Live: registry mirror reads Base mainnet · last block synced seconds ago · zero off-chain trust
Last 50 events on chain. Preview · illustrative until the chain mirror is wired through.
14:08 · 12s ago
VH-87FA-19C3-7E2D
Late Bloom — debut LP, side A
0xA1B2…dE4F
Anchored on Base
14:07 · 58s ago
VH-2D44-AA80-4B19
Skyline — sync placement v3
0x7F1c…9aD2
Anchored on Base
14:06 · 1m 42s ago
VH-91E3-5FCB-08A1
Sun Garden — visual EP intro
0x44e8…01F7
Anchored on Base
14:04 · 3m 21s ago
VH-7B0C-3DA9-9E15
Velvet Horizon — Album III, single
0xC3a9…7B2D
Anchored on Base
14:02 · 5m 47s ago
VH-66AB-12FE-77D8
Northbound — instrumental sketch
0x9d04…62E1
Anchored on Base
13:59 · 9m 03s ago
VH-04D1-A7B6-31C0
Halocline — vocal stem, master
0xB572…aF09
Anchored on Base
13:55 · 13m 18s ago
VH-EE21-9082-5C44
Drift Theory — sync edit
0x21F3…dC6B
Anchored on Base
13:51 · 17m 02s ago
VH-3F9A-6B11-D028
Tape Heaven — outtake reel
0x80aD…14C7
Anchored on Base
How registration works
Five steps from creation to a chain-anchored, license-ready work.
The registry is the spine. Every studio render, every upload, every license, and every split routes through the same primitive: a sealed work ID, committed to Base, addressable forever.
01Sealed work ID
The asset is hashed and bound to a creator key. The work ID is unique, verifiable, and travels with the file everywhere.
02Metadata commit on Base
Title, creator, asset hash, and timestamp commit to the Suede registry contract on Base mainnet (chain ID 8453).
03License slot opens
Each registered work exposes a license slot. Programmable terms can attach at registration or any later block.
04Splits attach
Royalty splits get bound to the work ID. Every payout the registry detects routes to the right wallet, on-chain, no human in the loop.
05Anyone can verify
Verification queries the chain, not us. Sync supervisors, labels, AI training services, and individuals all see the same source of truth.
Base · 8453L2 settlement layer
<2s verifychain query, no middleman
5,200+ worksand counting
LayerZero incross-chain bridge support
The registry is not a database with a chain badge stuck on top. It is a contract on Base, addressable by anyone, replaceable by no one.
Where the registry sits
Spine of the stack — everything reads from the same chain object.
Layer 04Marketplace, sync, and DSP delivery
Marketplace listings, sync placements, and DSP deliveries all reference the same registry record. No re-registration step at distribution time.
Layer 03Royalty distributor (Base)
The distributor consumes splits attached to the registry record. Monthly cadence, no human in the loop. Patent-pending USPTO 63/947,120.
Layer 02License templates + programmable terms
Splits, territory, royalty caps, and consent live as on-chain rules bound to the work ID. Buyers verify before they pay.
Layer 01Registry contract on Base
The on-chain object: asset hash, creator key, timestamp, license slot. Replaceable by no one, addressable by anyone.
Layer 00Sealed work ID
Hash + creator-key signature. The proof object that follows the work everywhere it travels, on or off chain.
About the Suede registry
The registry is the Suede primitive that everything else — vaults, studio, marketplace, royalties — reads from. One canonical record per work, one source of truth for everyone querying the rights state.
Base mainnet, chain ID 8453, L2 settlement layer
Sealed work IDs hashed and bound to creator key signatures
License slots open on every record — attach terms at any block
LayerZero bridge support for cross-chain inbound flows
A registry that is not on chain is just a database. Three things are only true because the Suede registry is a contract, not a service.
Lever 1
Verification with no middleman
Anyone — a sync supervisor, a label, an AI training service, a buyer — can query Base directly to confirm authorship, license, and royalty state. Suede is not the gatekeeper, the chain is.
Sub-2-second verification, zero off-chain trust, no API key required to read the source of truth.
Lever 2
Splits that survive the company
Royalty splits attached to the registry record are enforced by the distributor contract on Base. If Suede the company stops shipping tomorrow, the splits keep routing.
Programmable rights envelopes, contract-enforced, no clawback path. The contract is the marketing.
Lever 3
Cross-chain provenance, single record
LayerZero bridges cross-chain registration intent into the canonical Base record. The work has one ID across every chain, even when the creator's wallet does not.
Solana-native creators, EVM-native investors, and Base-native protocols all reference the same registry object. One spine, many arms.