Configuring Royalties on Magic Eden: EIP-2981, Solana, Enforced

Technical task: the contract must report royalties on-chain, and the marketplace must honor them. In practice, 90% of issues arise from standard incompatibility: ETH collections with EIP-2981 display correctly, Solana requires Metaplex configuration. Let's dive into each blockchain.

Royalties are the only way for a project team to earn revenue after NFT sales. But standards differ across blockchains, and marketplaces periodically change policies. We configure your collection's royalties so you receive payouts regardless of the platform.

The royalty wars of previous years shattered expectations for most NFT projects: Blur introduced optional royalties, trading volume leaked from OpenSea, and many collections lost their primary income source. Magic Eden went through several royalty policy iterations. Now the situation has stabilized, but configuration isn't a single button — it's a set of decisions at the contract and platform level.

How EIP-2981 Works

EIP-2981 adds a single function: royaltyInfo(uint256 tokenId, uint256 salePrice) returns (address receiver, uint256 royaltyAmount). The marketplace calls it before each trade, gets the receiver address and amount. This is a recommendation standard — the marketplace may ignore the response. OpenSea, Magic Eden (in enforced mode), and LooksRare honor it for compatible collections. Blur does not, unless the contract uses transfer blocking.

Implementation via OpenZeppelin takes 2–4 hours, requires ~20000 gas for deployment:

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

contract MyNFT is ERC721, ERC2981 {
    constructor() {
        // 5% royalty to team address
        _setDefaultRoyalty(teamAddress, 500); // 500 = 5% (basis points)
    }
}

For different token IDs you can set different royalties via _setTokenRoyalty. This is useful for collections with multiple tiers.

How Magic Eden Handles Royalties on Solana

On Solana the mechanics are different. Royalty is set in the NFT metadata via the seller_fee_basis_points field (0–10000, where 10000 = 100%) and the creators array with each one's share. This is part of the Metaplex Token Metadata standard. Magic Eden reads this data and pays royalties on sale through its program. Configuration takes about 3–5 hours via Sugar CLI.

EIP-2981 is implemented about 3 times faster than Metaplex setup, but the Solana approach is simpler for homogenous collections.

Example from practice: For a 10,000-item Ethereum collection we implemented EIP-2981 with 5% royalties. The deployment consumed 0.02 ETH in gas, and after verification on Magic Eden the royalties were automatically applied. The team now receives consistent revenue from secondary sales.

What Are Enforced Royalties and When Are They Needed?

Enforced royalties are the only way to technically compel royalty payment: restrict NFT transfers to approved marketplaces only. Implemented via the _beforeTokenTransfer hook with an operator allowlist. Magic Eden supports such collections through its operator filter. OpenSea launched the OperatorFilterRegistry but later abandoned it. Currently the most relevant approach is a custom allowlist in the contract.

The trade-off: strict enforcement reduces sales volume by 30–50%, but guarantees team income. Without enforcement, royalties can be zeroed out by marketplaces, as happened with Blur.

Configuration on Magic Eden

For Ethereum collections: A contract with EIP-2981 is automatically detected. In the Magic Eden Creator Hub dashboard, enter the collection address, verify ownership via signature. Royalties are displayed from the contract.

For Solana collections: Via Metaplex Sugar CLI or manual creation: set sellerFeeBasisPoints and creators at deploy time. Magic Eden verifies the collection through a request system — a verified badge is needed for full royalty display.

What's Included in Turnkey Configuration

• Audit of existing contract for EIP-2981 or Metaplex compatibility
• Implementation of royalties in contract (EIP-2981) or correction of Solana metadata
• Configuration of operator allowlist (enforced royalties) if desired
• Collection verification on Magic Eden (including request submission)
• Testing of royalty payouts on testnet (e.g., 5–10 trades)
• Documentation for royalty management
• Post-launch support for 30 days

Timeline Estimates

Configuring EIP-2981 in a new contract takes a few hours. Adding royalties to an existing contract without EIP-2981 is possible only via upgrade (if the contract is upgradeable) or deploying a new contract with migration. Collection verification on Magic Eden takes 1–3 business days on their side. We have been working with NFTs since the standard's inception and have implemented royalties for 50+ projects on Ethereum and Solana.

Contact us for a cost estimate for your collection. Order royalty configuration and get a consultation on the stack and timelines.

The EIP-2981 standard is described in the official Ethereum documentation.

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.