NFT Royalties Setup Guide: EIP-2981 and 0xSplits Integration

NFT royalties are no longer guaranteed after Blur's aggressive policy offering zero fees for traders. OpenSea responded by making creator royalties optional at the platform level. Result: most secondary sales occur without deductions if the collection does not use on-chain enforcement mechanisms. As blockchain engineers with 5+ years of Web3 experience and 50+ NFT collections launched, we help configure royalties so they actually work.

Two Approaches to Royalties and Their Reality

Off-chain Royalties (Marketplace Standard)

EIP-2981 is the on-chain standard for declaring royalties. The contract implements royaltyInfo(tokenId, salePrice), returning (receiver, royaltyAmount). OpenSea, Blur, and Rarible read this information and display it in the UI. But execution is at the marketplace's discretion. Technically, any trading smart contract can ignore EIP-2981 and not pay royalties, which most aggregators do.

On-chain Enforcement via Transfer Restrictions

The only way to guarantee royalties is to restrict token transfers: allow them only through whitelisted contracts (marketplaces) that pay royalties. This is the Operator Filter Registry, which Yuga Labs introduced for BAYC. Problem: transfer restrictions conflict with the ERC-721 standard. Aggregators not on the whitelist cannot trade the tokens. Some users perceive this as a restriction on their own asset rights. Consequently, Yuga Labs and OpenSea abandoned Operator Filter as a mechanism. In practice, most new collections implement EIP-2981 for correct display on marketplaces but do not restrict transfers. Royalties become a gentleman's agreement with the marketplace.

How We Configure Royalties: A Step-by-Step Process

1. Analyze the existing contract: check for EIP-2981 support, Solidity version, and used libraries.
2. Add EIP-2981: if the standard is missing, integrate OpenZeppelin ERC2981 or implement manually. If the contract is not upgradeable, deploy a new one with metadata migration.
3. Configure royalties in the contract: set a base percentage (usually 500 bps = 5%) via _setDefaultRoyalty or _setTokenRoyalty for specific tokens.
4. Split among participants: if royalties need to be divided, deploy a split contract via 0xSplits and set it as the receiver.
5. Verify on OpenSea: sign a transaction confirming contract ownership, configure Collection Settings.
6. Test: purchase a test token on the secondary market and verify royalty receipt.

Why EIP-2981 Is Not Enough

Marketplaces can ignore on-chain data. OpenSea still respects EIP-2981, but Blur and aggregators often set zero royalties. Alternatives include using operator filters or ecosystem solutions like the Royalty Registry. However, these are trade-offs: every additional restriction reduces liquidity. In one of our projects, a collection using Operator Filter saw a 40% drop in trading volume due to exclusion of popular aggregators. Using 0xSplits instead of a custom split contract is 3x more gas-efficient for each royalty payout. Gas savings reach 40%, which at an average gas price of 30 gwei saves approximately $5 per 1000 transactions (based on ETH at $2000). Deploying a split contract costs around $20 in gas, and each distribution call costs $2.

How to Split Royalties Among Participants

If royalties need to be distributed among the team, do not write the split logic into the NFT contract. Use 0xSplits or Splits Protocol: deploy a split contract with shares, set its address as the receiver in EIP-2981. When ETH arrives at the split address, anyone can call distribute() — funds are automatically split according to the configured shares. Writing a custom split in the contract increases gas by 30–50% on each sale, whereas 0xSplits requires only one external transaction for distribution. Comparison: 0xSplits is 3x more gas-efficient than a custom split contract, reducing costs by 40%.

EIP-2981 combined with 0xSplits allows flexible royalty management without complicating the main contract.

Scope of Work

• Audit of the existing contract for EIP-2981 compatibility.
• Deployment or upgrade of the contract with royalty support (if necessary).
• Configuration of splits through proven protocols.
• Verification on OpenSea and test sales.
• Documentation on contract interaction.
• Support for one month after deployment.

We offer a turnkey solution: audit, deployment, and verification in 2 hours. Includes everything: smart contract modifications, split configuration, and one month support. Contact us for a free estimate — we will evaluate your project and provide a fixed price. Our team has 5+ years of Web3 experience, 50+ NFT projects launched, and verified over 100 collections on OpenSea. Get a consultation with an engineer to discuss details.

Comparison of Royalty Approaches

Estimated Timeline

Contact us — we will discuss your project and choose the optimal solution. Write to us for a free estimate.

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.