NFT Marketplace Aggregator Development: Best Prices & Bulk Buy

We develop NFT marketplace aggregators that solve the liquidity fragmentation problem. Why open four tabs when you can buy an NFT at the best price in one click? Our aggregators unite OpenSea, Blur, LooksRare, X2Y2, and other platforms, collecting all orders into a single listing and executing the trade via the optimal route. Projects like Gem.xyz and Reservoir have become industry standards, but for specialized niches (gaming, phygital, traits), huge potential remains.

Assess your project for free — contact us.

How does an NFT aggregator work?

An aggregator is a combination of smart contracts and backend infrastructure. Smart contracts enable atomic purchase of multiple NFTs in one transaction, while the backend indexes orders from all platforms and provides an API for the frontend. The frontend displays a unified list, allows filtering by traits, price, and source, and enables a cart for bulk purchases.

Architecture at the smart contract level

Executing multi-marketplace trades

The key component is the aggregator contract, which in one transaction buys NFTs from several platforms:

contract NFTAggregator {
    struct TradeData {
        address marketplace;
        bytes tradeData;      // calldata for specific marketplace
        uint256 value;        // ETH for this part of trade
        bool isERC721;
    }

    function batchBuy(TradeData[] calldata trades) external payable {
        for (uint256 i = 0; i < trades.length; i++) {
            (bool success, ) = trades[i].marketplace.call{value: trades[i].value}(
                trades[i].tradeData
            );
            if (!success) {
                // Partial fill or revert depending on policy
                emit TradeFailed(i, trades[i].marketplace);
            }
        }
        // Return unspent ETH
        if (address(this).balance > 0) {
            payable(msg.sender).transfer(address(this).balance);
        }
    }
}

Why is atomicity of transactions important?

If the first 3 NFTs are bought, but the 4th is already sold — what to do? Two modes: failOnRevert (revert everything if any trade fails) and skipFailed (buy what you can, return funds for the rest). Gem used the second approach as a UX optimization — the user still gets part of what they requested. Atomicity is critical for sweeps, where a transaction can include dozens of orders.

Order format support

Each marketplace has its own standard:

For each, a separate adapter is needed. Seaport is the most complex: supports criteria-based orders (can buy any token from a collection with certain traits), advanced orders with partial fill, multiple recipients for royalties. Seaport protocol specification

Sweeping and trait-based purchases

Sweep (mass buying from the bottom of the price range) is the main function for collectors and traders. Trait-sweep: buy all "legendary" available, regardless of marketplace. Requires criteria-based matching in Seaport or off-chain filtering with on-chain execution.

Indexing and data layer

An aggregator without up-to-date data is useless. 90% of the complexity lies in the infrastructure for collecting and updating orders.

Data sources

• Marketplace APIs: OpenSea API v2, Blur API (partially closed), Reservoir protocol as a meta-aggregator with open API. Reservoir indexes most marketplaces and provides a unified API — it's reasonable to use it as a foundation, adding custom indexing for specific cases.
• On-chain events: listen to OrderFulfilled, OrderCancelled events from Seaport and similar on other marketplaces. WebSocket subscription via Alchemy/Infura for real-time updates. A delay of 1-2 blocks is acceptable for most use cases.
• Custom indexer: for production — a custom indexer based on The Graph subgraph or a custom solution in Go/TypeScript. Store orders in PostgreSQL with indexes on (contract, tokenId, price). Redis for hot data (floor price, recent sales).

The staleness problem

Orders become stale. The best listing on OpenSea may already be executed by the time the user clicks "Buy". Solutions:

• On-chain status check before display (expensive in RPC calls)
• Optimistic UI with fallback to the next best order on failure
• Cache with TTL 30 seconds + real-time invalidation via events

Blur adds extra complexity: the bid pool shows "available" bids that may be filled by competitors faster than your transaction arrives.

Frontend architecture

Search and filtering

Full-text search by collection name + filters: trait-based, price range, marketplace source, verification status (verified/unverified collection). Elasticsearch or Meilisearch for fast search over millions of tokens. Virtualized list (react-virtual or tanstack-virtual) — collections with 10k tokens are not rendered in the DOM completely.

Cart

An aggregator without a cart is just a search engine. Cart: add several NFTs from different marketplaces, show total cost + gas estimate, execute in one transaction. Technically, forming a TradeData[] array on the frontend with a subsequent call to batchBuy(). Gas estimation for batch transactions is non-trivial: each marketplace consumes different gas, plus aggregator overhead. Use eth_estimateGas with a small buffer (10-20%) or a precomputed gas lookup table by marketplace type.

Royalty compliance

After Blur introduced optional royalties and captured market share, the topic became political. The aggregator must clearly show which royalties will be paid for each purchase and let the user choose — either apply project policy automatically (based on on-chain royalty registry EIP-2981 + Manifold Registry).

Monetization and competitive positioning

Standard models: 0.5-1% fee on volume, pro subscription for analytics, API access for other projects. Blur disrupted listing fees — compete on UX, speed, analytics, specialization (niche chains, specific categories like gaming NFTs, phygital). Multichain is a must: Ethereum, Polygon, Base, Arbitrum, Blast. Each chain needs a separate indexer, but the aggregator contract and frontend are unified.

Stages of NFT aggregator development

1. Requirements analysis: define target audience, functionality (sweep, traits, cross-chain), list of marketplaces.
2. Smart contract design: develop batchBuy architecture, adapters for each marketplace, test on fork networks.
3. Indexing layer development: set up indexers, integrate with APIs and on-chain listeners, caching.
4. Frontend: UI/UX design, implement search, cart, wallet integration (MetaMask, WalletConnect).
5. Testing: unit tests for contracts (Foundry), fuzzing (Echidna), integration tests on testnet.
6. Security audit: check contracts via Slither/Mythril, external audit.
7. Deployment and monitoring: deploy on mainnet, configure Tenderly, Grafana.

What is included in the work

• Development of smart contracts for aggregator and adapters for 5+ marketplaces
• Backend order indexing (custom indexer or based on Reservoir)
• Frontend with search, filtering, cart, and wallet integration
• Multichain integration (Ethereum, Polygon, Arbitrum, Base)
• Security audit and gas optimization
• API and smart contract documentation
• Post-launch support (3 months)

Estimated timelines

Cost is calculated individually depending on complexity and number of integrations.

Our team has 5+ years of experience in blockchain development and has delivered over 20 projects in the DeFi and NFT space, including marketplace aggregators. We guarantee compliance with modern security standards and gas optimization.

Assess your project for free — contact us for a consultation.

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.