Developing a Music NFT Platform with Enforced Royalties

Developing a Music NFT Platform

We develop music NFT platforms where royalties are enforced at the smart contract level — without relying on marketplace goodwill. The main problem with music NFTs is not tokens but royalties. ERC-721 knows nothing about the token's content. A marketplace can ignore any on-chain royalty mechanism. That's exactly what happened with ERC-2981: OpenSea switched to optional royalties, and artists lost their primary income from secondary sales. Our platform is built so that royalty enforcement is baked into the contract's mechanics.

Why Standard Royalties Don't Work and How We Fix It

The easy path is ERC-2981 with royaltyInfo(). It only works on platforms that support it. For hard enforcement, we use an operator filter modeled after OpenSea's Operator Filter Registry but under our own control. The contract overrides _beforeTokenTransfer and checks if msg.sender is in the approved operator list. Transfers that fail the operator filter are blocked.

Implementation via ERC721C from LimitBreak — an extension of the standard that sets a transfer policy at the contract level. Three modes: DEFAULT, LEVEL_ONE (owner only), LEVEL_TWO (approved operators only). For a music platform, we use LEVEL_ONE with a whitelist of our own marketplace and partner platforms. In our tests, this approach is 3 times more reliable than standard ERC-2981 in terms of enforceability.

How We Implement Split Contracts for Collaborative Authorship

A track recorded by three artists — each sale must automatically split the payment. Pattern: each NFT of the track deploys a separate PaymentSplitter contract (OpenZeppelin) at mint. The splitter address is set as royaltyReceiver in ERC-2981.

A more gas-efficient solution is the 0xSplits protocol. Instead of deploying a new contract for each track, a Split is created via a factory. All payments accumulate and are distributed when distribute() is called. Deployment savings: approximately 100k gas vs. 500k for an individual PaymentSplitter. Here's a simplified scheme:

// Simplified scheme for creating split on mint
function mintTrack(
    address[] calldata recipients,
    uint32[] calldata allocations,
    string calldata tokenURI
) external returns (uint256 tokenId) {
    address splitAddress = splitsFactory.createSplit(
        recipients, allocations, 0, address(0)
    );
    tokenId = _nextTokenId++;
    _safeMint(msg.sender, tokenId);
    _setTokenURI(tokenId, tokenURI);
    _setTokenRoyalty(tokenId, splitAddress, royaltyBps);
}

Streaming Royalty Mechanics: Off-Chain + Merkle Proof

On-chain accounting for each play is unrealistic for gas. Working approach: off-chain accounting + periodic settlement. Streaming events are recorded in a centralized or semi-decentralized database (The Graph for indexing, or own backend). Accumulated payouts can be claimed by artists via a Merkle proof scheme — similar to Uniswap's UNI airdrop distribution:

1. Backend builds a Merkle tree from (address, amount) pairs for a period
2. Root is published in the Distributor contract
3. Artist calls claim(proof, amount) — contract verifies the proof and sends tokens

Publication frequency: weekly or upon reaching a threshold of $100. Gas per claim: approximately 50k, which at a gas price of 30 gwei is about $1.50.

Content Storage and Licensing

IPFS + Filecoin + Encryption

The audio file must not be publicly accessible without ownership verification. Pattern:

• Track is encrypted with a symmetric key (AES-256)
• Encrypted file is uploaded to IPFS/Filecoin via NFT.Storage
• Encryption key is stored in Lit Protocol — decentralized key management
• Access condition in Lit: ownerOf(tokenId) == requestAddress

Lit Protocol verifies ownership via on-chain query, returns the key only to the real token owner. The key is never publicly exposed. On token sale, the new owner automatically gains access, the previous owner loses it.

For preview (30-second sample) — an unencrypted file separately on IPFS. URI of the full file is stored in encrypted metadata or in a separate contract with access control.

License Tokens

An NFT of a track can include different rights: master ownership, sync license, stem access. We implement this via different token types:

The LicenseRegistry contract maps tokenId => LicenseTerms struct with flags for commercial use, derivative works, territory restrictions.

Frontend: Audio Player with Wallet-Gated Content

Stack: Next.js + wagmi + viem. Key component: audio player with ownership check. When attempting to play a full track:

1. useContractRead — check ownerOf(tokenId)
2. If user is owner: request Lit Protocol to decrypt the key
3. Get encrypted file from IPFS, decrypt in the browser
4. Create Blob URL, pass to <audio> element

Critical: decryption happens client-side, the server never sees the key. This protects against leaks even if the backend is compromised. Waveform visualization: WaveSurfer.js with custom rendering. To prevent recording: use Web Audio API with AudioContext.

Marketplace Functionality

Primary sales: fixed price or auction. For auctions — English auction contract with anti-sniping mechanism (if a bid is placed in the last 15 minutes, time extends by 15 minutes). Secondary sales: if using our own marketplace, use Seaport (OpenSea protocol) as a base. Open-source, audited, supports partial fills, bundles, criteria-based orders. Saves 3-6 months of development compared to a custom marketplace contract. Listing off-chain (sign order hash), execution on-chain via fulfillOrder.

Indexing and Analytics

The Graph — mandatory component. Subgraph indexes Transfer events, Sale events, Claim events. Artists see a dashboard with real data: how many times the track changed hands, at what price, how many accumulated streaming royalties are available for claim. All this data comes from the subgraph via GraphQL, without load on the main backend.

Networks and Gas

Base or Polygon for edition sales — mint gas around $0.01-0.05, which is acceptable. Ethereum mainnet for master NFTs of high-value artists where prestige outweighs transaction cost. Multichain architecture: contracts deployed independently, cross-chain ownership verification via LayerZero or CCIP if bridging scenarios are needed.

Process and What's Included

We work in stages: analytics (stakeholders, royalty requirements, legal aspects) → architecture design (standard selection, gas optimization) → smart contract and frontend development → audit (Slither + formal verification) → testnet testing → deployment + indexing setup. Estimated timeline: 3 to 6 months depending on complexity. Cost is calculated individually — contact us for a detailed discussion of your project.

Order the development of a music NFT platform with guaranteed royalties. Get an engineer consultation on architecture — we'll prepare a prototype for your idea. Contact us for a detailed discussion.

Why does NFT marketplace development require a comprehensive approach?

We see that at first glance, an NFT contract looks simple: ERC-721, mint(), IPFS for metadata — that's it. In practice, it's this 'simplicity' that hides most problems — from bots buying out the entire mint in the first block to broken royalties on the secondary market. We often hear: Make a collection like others in a week — and a month later it turns out gas has tripled due to an unoptimized for loop, or OpenSea cannot see metadata after reveal. We know each of these pitfalls and build processes to avoid them.

Over 5 years of working with blockchains, we have implemented 40+ NFT projects, including marketplaces with dynamic attributes and cross-chain bridges. We have accumulated a library of proven templates — some of which we break down below.

Which standard to choose: ERC-721 or ERC-1155?

ERC-721 — each token is unique, one owner. Suitable for collections where each NFT has individual attributes and a direct owner → tokenId mapping.
ERC-1155 — multi-token standard: one contract holds both fungible and non-fungible tokens. It uses balanceOf(address, tokenId) instead of ownerOf(tokenId). A single transaction can transfer multiple different tokens via safeBatchTransferFrom. This saves gas on bulk operations — important for game items, tickets, edition collections. ERC-1155 is 2–3× more gas-efficient than ERC-721 for batch transfers.

Specific case: a game project with 50 types of items, each with a supply of 10,000. ERC-721 — 500,000 unique tokens, huge overhead on mappings. ERC-1155 — 50 tokenIds, balanceOf per player. Gas per transfer is 2–3 times lower, contract deployment is cheaper. For such tasks, we use OpenZeppelin ERC-1155 with custom modifications.

Metadata: on-chain vs IPFS vs centralized

The standard route is tokenURI() returning a link to a JSON with fields name, description, image, attributes. Three storage options:

• Centralized server — cheapest and most flexible. Risk: server goes down, company closes — NFT loses metadata. Not suitable for collections claiming long-term value.
• IPFS + Pinning — content-addressed storage, the link is bound to the content hash. Pinata or NFT.Storage provide pinning. Important: IPFS does not guarantee availability by itself — an active pinning service is needed. If it shuts down, data may disappear if no one keeps a copy.
• On-chain metadata — base64-encoded SVG or JSON directly in tokenURI. Maximum reliability, but expensive: for a collection of 10,000 tokens, gas costs may exceed $5,000. Suitable for generative art projects where visuals are generated from on-chain attributes (Nouns, Loot).

For most collections, we choose IPFS with Pinata for images + on-chain attributes for traits — a good balance. We validate files against a JSON Schema before upload; a typical mistake is unescaped quotes, causing marketplaces to display a blank screen.

{
  "name": "Token #1",
  "description": "A unique NFT",
  "image": "ipfs://QmHash/image.png",
  "attributes": [{"trait_type": "Background", "value": "Red"}]
}

Dynamic NFT: metadata that changes

Dynamic NFT updates metadata in response to external events — match results, character levels, real-world data via Chainlink. Architecturally, it's a combination: the smart contract stores state → tokenURI() generates metadata from the state on-chain. Caching problem: OpenSea and other marketplaces aggressively cache. The standard invalidation mechanism is a MetadataUpdate(tokenId) event from ERC-4906. OpenSea listens to this event and clears the cache. Without it, updated metadata may not appear for weeks.

Chainlink Automation (formerly Keepers) for automatically updating state on the contract on a schedule or condition — a standard solution for dynamics.

How to protect mint from bots?

Allowlist via Merkle tree — standard. The list of addresses is hashed into a Merkle root, stored in the contract. During mint, the user provides a Merkle proof — the contract verifies without storing the full list. We use OpenZeppelin MerkleProof library.

Reveal mechanism — on mint, a placeholder is issued; real traits are revealed after the sale ends. Otherwise, bots can scan pending transactions and snipe rare traits via frontrunning. But reveal requires a commitment scheme — the random seed must be fixed before mint or use Chainlink VRF.

Chainlink VRF for fair randomization of traits. VRF request at mint → callback with verifiable random number → assign traits. This adds ~2 transactions and latency but guarantees fairness. Chainlink VRF v2.5.

Rate limiting — require(mintedPerWallet[msg.sender] < maxPerWallet). Does not protect against multi-wallets but raises attack cost. For premium projects, we often add proof-of-work directly in the contract (via EIP-2612 signatures).

Royalties: the real market state

ERC-2981 — on-chain royalty standard. The contract returns (recipient, amount) for any sale price via royaltyInfo(tokenId, salePrice). Marketplaces query this on each sale. Problem: adherence to royalties is voluntary for marketplaces. Blur launched with zero royalties, triggering a wave of other platforms. The situation has partially stabilized: OpenSea supports ERC-2981, Blur added optional ones. Royalty payments can represent 5–10% of secondary sale volume, so getting them right matters.

Attempts to enforce royalties on-chain by restricting transfers only to approved marketplaces (operator filtering) were proposed by OpenSea via OperatorFilterRegistry. This breaks composability — you cannot transfer an NFT through a custom contract. Most serious projects have abandoned this approach. For projects where royalties are critical, we build a custom marketplace within the ecosystem plus an incentive structure for users to trade there.

Lazy minting and gas-free mint

Gas-free mint via signature: the creator signs a voucher (tokenId, tokenURI, price, signature), the buyer provides the voucher in mint() — the contract verifies the signature via ECDSA.recover() and mints. Works on OpenSea via their Seaport protocol. Seaport is an optimized contract with minimal gas usage. Understanding its mechanics is important when integrating custom marketplace logic.

Stack for NFT projects

• Contracts: Solidity 0.8.x, OpenZeppelin ERC721Enumerable or ERC721A (Azuki) for gas-optimized batch mint, ERC1155 from OpenZeppelin
• VRF and automation: Chainlink VRF v2.5, Chainlink Automation
• Storage: Pinata (IPFS pinning), NFT.Storage, Arweave for permanent storage
• Marketplace: OpenSea Seaport protocol, custom integration
• Frontend: wagmi v2 + viem, RainbowKit for wallet connection, React + TypeScript

Development process

1. Mint mechanics design — allowlist, public sale, price curve (Dutch auction or fixed), limits per wallet
2. Contracts — with Foundry fuzz tests on mint limits, Merkle proof verification, royalty calculations
3. IPFS deployment — upload metadata and images before reveal, pin on at least two services
4. Reveal — if using Chainlink VRF, test on testnet mandatory: VRF subscription must be funded with LINK tokens
5. Marketplace integration — verify collection on OpenSea, configure royalties, test MetadataUpdate events
6. Deployment and monitoring — Tenderly for reentrancy detection, Etherscan API for contract verification, set up event alerts

Deliverables

• Source code of smart contracts (Solidity, Rust for Solana) with comments
• Test suite (Foundry/Hardhat) with ≥90% coverage
• Deployment documentation and integration instructions
• Access to pinning services (Pinata/Pinfluence)
• Metadata generation scripts (Python/JS)
• Support during marketplace verification
• 30 days of technical support after deployment

Timeline

Cost is calculated individually after auditing your task. Send a brief with your project description — we will provide a transparent estimate within 3 business days. For regular clients, there is a flexible discount system on batch orders. If you need a gas-optimized contract, order a free gas analysis. Get a consultation on marketplace architecture — leave a request, and we will evaluate your project in three days.