Skip to main content
A Rawchunks license enables its ongoing remix workflow. Purchasing reduces the original’s available allocation; making another remix does not consume the buyer’s license. Remixes cannot be licensed or remixed again in this workflow. Use the same network for the original, license purchase and remix mint. The license price comes from the confirmed chain record, not a cached catalog price.

Verify the original

Use the EVM setup and factoryAbi from Factory reads. Set sourceSongId to the original’s catalog ID. Load it with the request client, then read its contract song:

Buy and confirm

Follow Remix’s purchase example with this originalSongId, its verified state and the buyer’s connected wallet. It reads existing rights, approves the actual settlement token when needed, sends buyLicense and verifies Factory.hasLicense after confirmation. Show the chain price and settlement currency before requesting signatures. Store the approval and purchase hashes as soon as your wallet returns them. Recover an interrupted confirmation from those hashes before retrying. For license payments, 80% goes to the original creator and 20% to the Rawchunks treasury. Session service fees and wallet costs are separate.

Open and edit the draft

Check the caller’s chain license before this request. The REST draft route does not purchase or verify that license. It creates a private song with source linked to the original and zero license allocation. Use the returned ID for editing.

Mint the finished variation

Pin the finished draft JSON to get remixCid, using the metadata step. Set metadataUri to ipfs:// followed by remixCid. In Remix’s variation call, use: Keep the original and remixer identities in the final metadata. After the successful receipt, use the Factory event example to obtain mintedId. Check the new song’s creator, URI, isRemix = true and parentSongId = originalSongId. Then record the result with the remixer’s request headers:
A mint or license button does not establish copyright ownership, exclusivity or permission for outside distribution. Obtain any additional rights your product needs from the rights holder. The API and contract enforce the Rawchunks workflow described here. For Solana accounts, use the Solana license and remix example.