← all templates/Recording

Recording royalty split

Mint a Muzix catalog token for a recording and lock the cap table on-chain. Artist + producer + label + publisher style.

01 · parties

name	role	address	share (bps)

100.00%/ 100%

02 · terms

Track title *Artist (display) *ISRC *Release dateTerritorySpecial terms / notes

03 · validation

✗ parties.0.name Party #1: name required.
✗ parties.0.address Party #1: needs a valid 0x address.
✗ parties.1.name Party #2: name required.
✗ parties.1.address Party #2: needs a valid 0x address.
✗ parties.2.name Party #3: name required.
✗ parties.2.address Party #3: needs a valid 0x address.
✗ parties.3.name Party #4: name required.
✗ parties.3.address Party #4: needs a valid 0x address.

draft · plain english

# Recording Royalty Agreement
**Title:** [title]
**Performing artist:** [artist]
**ISRC:** [ISRC]
**Release date:** 2026-05-24
**Territory:** Worldwide
## 1. Parties & cap table
The parties below agree to the proportional split of net recording revenue, enforced on-chain by the MuzixCatalog royalty-split mechanism (basis points, 10000 = 100%):
- [unnamed party] (Artist) — [address pending] — 60%
- [unnamed party] (Producer) — [address pending] — 20%
- [unnamed party] (Label) — [address pending] — 15%
- [unnamed party] (Publisher) — [address pending] — 5%
## 2. Revenue settlement
Streaming platforms and licensees deposit revenue into the token's on-chain balance via `depositRevenue(tokenId)`. Each party withdraws their pro-rata share via `claimStreamingRevenue(tokenId)`. No party shall be entitled to a distribution exceeding their share above.
## 3. Provenance
The parties attest that this recording is human-authored unless an AI-provenance record is subsequently attached via the MuzixAIProvenance registry by the catalog token owner.
## 4. Governing protocol
Settlement is governed by the MuzixCatalog contract on chain ${chainId}. The signed token URI is the canonical metadata reference.

onchain · plan

mode · live · chain 1338

· Step 1 mints the catalog token to your connected wallet.
· Step 2 is sent from the same wallet; the token owner is the only address allowed to set the split.

step 1 · MuzixCatalog.mintMusic
mintMusic(tokenURI, {isrc:"", artist:""})
step 2 · MuzixCatalog.setRoyaltySplit
setRoyaltySplit(<newTokenId>, 4 recipients, shares totaling 100%)

04 · deploy

⚠ Live contracts aren't configured for this build — setNEXT_PUBLIC_MUZIX_CATALOG + NEXT_PUBLIC_MUZIX_AI_PROVENANCE. You can still copy encoded calldata below.

encoded calls preview

step 1 → 0x0000000000000000000000000000000000000000 :: MuzixCatalog.mintMusic
0xd639525e00000000000000000000000000000000000000000000000000000000000000400000000000000000000000000000000000000000000000000000000000000080000000000000000000000000000000000000000000000000000000000000001f697066733a2f2f6d757a69782f6e6f2d697372633a756e7469746c65643a34000000000000000000000000000000000000000000000000000000000000000040000000000000000000000000000000000000000000000000000000000000006000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000

step 2 → 0x0000000000000000000000000000000000000000 :: MuzixCatalog.setRoyaltySplit
0x315e0c2c000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000600000000000000000000000000000000000000000000000000000000000000100000000000000000000000000000000000000000000000000000000000000000400000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000004000000000000000000000000000000000000000000000000000000000000177000000000000000000000000000000000000000000000000000000000000007d000000000000000000000000000000000000000000000000000000000000005dc00000000000000000000000000000000000000000000000000000000000001f4