Enforced NFT Royalties: From ERC-2981 to Custom Whitelists

Enforced Royalties in NFT: From ERC-2981 to Custom Whitelists

You launched a collection of 10,000 NFTs, invested millions in art and marketing, and a month later you see your royalties aren't being paid. Marketplaces used to do it automatically, but then Blur introduced zero fees, and some platforms stopped honoring EIP-2981. Creators lost millions. The choice between on-chain enforcement and voluntary payments became a product decision, not a technical one. We implement both approaches, add custom logic, and guarantee royalties reach you. With secondary trading volume of 100 ETH, a 7.5% royalty brings 7.5 ETH — but only if enforced. Get a consultation — contact us to start with a free audit.

How to Ensure Enforced Royalty Payments?

ERC-2981: Basic but Optional

ERC-2981 is a signaling standard. The contract declares royaltyInfo(tokenId, salePrice), the marketplace reads it and (optionally) pays. Blur may ignore it. OpenSea honors it. Magic Eden — depends.

Implementation via OpenZeppelin takes 10 lines:

import "@openzeppelin/contracts/token/common/ERC2981.sol";

contract MyCollection is ERC721, ERC2981 {
    constructor(address royaltyReceiver) ERC721("Collection", "COL") {
        _setDefaultRoyalty(royaltyReceiver, 750); // 7.5%
    }
    
    function supportsInterface(bytes4 interfaceId) 
        public view override(ERC721, ERC2981) returns (bool) {
        return super.supportsInterface(interfaceId);
    }
}

Without the supportsInterface override, the marketplace won't detect ERC-2981 support during ERC-165 checks. This is a common mistake we've encountered in 10+ audits.

Operator Filter: Enforced Collection

If royalties are commercially important, you need an operator filter. The idea: the contract checks every transferFrom and safeTransferFrom, only allowing transfers through approved marketplaces that honestly pay royalties. Operator Filter is 2-3 times more reliable than pure ERC-2981 in guaranteeing payments.

OpenSea proposed the OperatorFilterRegistry.

import {DefaultOperatorFilterer} from "operator-filter-registry/src/DefaultOperatorFilterer.sol";

contract MyCollection is ERC721, ERC2981, DefaultOperatorFilterer {
    function transferFrom(address from, address to, uint256 tokenId) 
        public override onlyAllowedOperator(from) {
        super.transferFrom(from, to, tokenId);
    }
    
    function safeTransferFrom(address from, address to, uint256 tokenId) 
        public override onlyAllowedOperatorApproval(from) {
        super.safeTransferFrom(from, to, tokenId);
    }
}

onlyAllowedOperator checks the operator address against the registry. Blur was initially blocked, then added after negotiations.

Compromise: the operator filter protects royalties but limits liquidity — users cannot trade on unapproved platforms. For some collections this is unacceptable.

Why ERC-2981 Alone Is Insufficient for Royalty Protection?

ERC-2981 without a filter is just a promise. Operator filter gives on-chain guarantee. If your project is designed for long-term sales and plans to earn from royalties, the filter pays off. For art collections with high secondary activity, we recommend it. Our experience: over 20 projects used the filter and increased royalty income by 30-50% compared to pure ERC-2981.

How to Set Up a Custom Marketplace Whitelist?

Independence from OpenSea's registry — via custom logic. Approach: allow transfer only if initiated through whitelisted contracts (marketplaces that have explicitly integrated our royalty mechanism), or if it's a wallet-to-wallet transfer (not via a marketplace).

mapping(address => bool) public approvedMarketplaces;

function _beforeTokenTransfer(address from, address to, uint256 tokenId) 
    internal override {
    // Allow direct transfers (not via marketplace)
    if (from == tx.origin || to == tx.origin) return;
    // Check that the marketplace is approved
    require(approvedMarketplaces[msg.sender], "Marketplace not approved");
}

This is less flexible but independent of external registries. As market conditions change, you add or remove platforms yourself without waiting for an OpenSea registry update.

Splitter for Teams

If royalties are split among multiple addresses, set the receiver in ERC-2981 to a PaymentSplitter:

address[] memory payees = [founder, artist, treasury];
uint256[] memory shares = [50, 30, 20];
PaymentSplitter splitter = new PaymentSplitter(payees, shares);
_setDefaultRoyalty(address(splitter), 500); // 5% royalty to splitter

Each recipient calls splitter.release(token) to collect their accumulated funds. Pull pattern — no reentrancy risk from automatic distribution.

Comparison of Royalty Approaches

Common Mistakes and Their Consequences

For an updatable receiver, add updateDefaultRoyalty() with onlyOwner:

function updateDefaultRoyalty(address receiver, uint96 feeNumerator) 
    external onlyOwner {
    _setDefaultRoyalty(receiver, feeNumerator);
}

Step-by-Step Guide to Implementing Operator Filter

1. Install the operator-filter-registry package via npm or Foundry.
2. Inherit your contract from DefaultOperatorFilterer.
3. Add the onlyAllowedOperator and onlyAllowedOperatorApproval modifiers to transfer functions.
4. Test on a testnet like Rinkeby or Goerli.
5. Deploy on mainnet and verify that transfers through approved platforms work.

What's Included in Turnkey NFT Development with Royalties

• Smart contract with ERC-2981 or operator filter
• Custom enforcement logic (if needed)
• PaymentSplitter for royalty distribution
• Minting and interaction scripts
• Deployment and update documentation
• 30-day support after deployment

Timeline Estimates

NFT contract with ERC-2981 royalties and PaymentSplitter — 2-3 days. With operator filter and custom enforcement logic — 3-4 days. We'll evaluate your project within a day. Ready to discuss details? Contact us — we'll start with a free audit of your current contract.

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.