← Protocols
Royal
NFT / Marketplace·Ethereum · Polygon

Royal

01Description

Music IP tokenization platform: artists fractionalize streaming royalty rights as Limited Digital Assets (ERC-1155) with on-chain royalty distribution.

02Best for
  • 01music royalty fractionalization
  • 02artist-fan revenue sharing
  • 03streaming royalty distribution
  • 04music IP marketplaces
  • 05fan ownership programs
04Environment variables
VariableScopeDescription
ROYAL_API_KEYServerRoyal partner API key (request via Royal partnerships team) for catalog and ownership reads.
05Prompt snippet
Use Royal to surface music IP ownership and royalty distributions. Royal does not currently expose a public SDK — integrate by querying the LDA ERC-1155 contract directly with viem's `useReadContract({ address: ldaContract, functionName: 'balanceOf', args: [user, tokenId] })` to read per-song share counts. Distributions are pushed via a dispersing contract on a periodic basis; subscribe to its `RoyaltyDistributed(tokenId, amountUSDC)` events to compute per-holder yield. For catalog metadata + KYC-gated mint flow, deep-link to the Royal hosted page rather than minting directly.
06Gotchas
  • LDAs are KYC-gated at the mint and (in some cases) at transfer — secondary trades via OpenSea/Blur can revert against the whitelist registry; gate UI on `kycRegistry.isApproved(address)` before showing buy buttons.
  • Royalty enforcement is off-chain (legal + dispersing contract), not EIP-2981 — secondary marketplaces will not pay artist creator fees automatically; the only revenue holders earn is the streaming royalty distribution, not resale.
  • Chain coverage is limited to Ethereum and Polygon; LDAs do not bridge — bridging will sever the holder from the dispersing contract's snapshot and forfeit future payouts.
  • Distributions use USDC, and snapshot timing is contract-controlled — buying mid-period does NOT entitle you to that period's payout; always read the `lastSnapshot` timestamp before showing 'expected yield'.
  • Royal restructured publicly in 2024–2025; treat the platform as discontinued for new artist signups and integrate as 'historic catalog only' unless you've confirmed otherwise with the team.
  • Metadata for songs is hosted on Royal's CDN, not IPFS — long-term display requires snapshotting the JSON yourself or it can disappear if the platform sunsets.
07Alternatives