White-Label NFT Marketplace Development
OpenSea processes billions of dollars annually through one set of smart contracts — Seaport. Same contract used by dozens of marketplaces via white-label integrations. Developing trading logic from scratch in 2024 is impractical: Seaport passed multi-level audit, supports all current standards (ERC-721, ERC-1155, ERC-20 as payment), has optimized gas layout. White-label marketplace task — business logic, branding, UX and customizations on top of proven protocol.
What We Build on Seaport
Trading Logic and Order Types
Seaport supports flexible order system via OrderComponents. Basic cases for marketplace:
Fixed price listing — seller creates signed order (off-chain, no gas), buyer executes via fulfillOrder(). Signature stored in our database or decentralized orderbook.
Auction — Dutch (descending price) or English (bidding). For English auction need on-chain bid handling logic — each bid is transaction, expensive on Ethereum mainnet. Alternative: off-chain bids with signatures, on-chain winner finalization.
Bundle trading — Seaport natively supports bundled orders: one transaction to buy group of NFTs. Built into protocol, requires no additional contracts.
Collection offers — offer on any token from collection. Seller can accept offer for any of their tokens. Implemented via Seaport criteria-based orders with Merkle root of collection.
Protocol Fees
Seaport doesn't charge fees — platform does. Fee set in each order as consideration item: when creating listing, user signs order that includes platform fee transfer (1-2.5%) to treasury address. Can't change fee retroactively — buyer protection.
EIP-2981 royalties handled same way: when creating order, frontend reads contract royaltyInfo and adds royalty payment to consideration. If marketplace doesn't add — royalties won't be paid (see problem with optional royalties).
Contract Level: What We Customize
Zone contracts — Seaport supports zones: additional order validation on execution. Use for:
- Token-gated trading (only holders of specific collection)
- Geographic restrictions (off-chain verification via signature)
- Custom conditions (order valid only until specific block)
ConduitController — manages approved transfer operators. Conduit allows users to give approval once, and all marketplaces using this conduit can execute transfers. Reduces approve-transactions count.
Custom ERC-721 for platform collections — if marketplace also allows minting collections (creator marketplace), need factory contract for collection deployment and royalty management system.
Frontend and Indexing
Displaying NFTs and order state requires off-chain indexing — querying blockchain on every page load unacceptable due to latency.
The Graph — subgraph for Seaport events (OrderFulfilled, OrderCancelled, OrderValidated) and collections (Transfer, Mint). GraphQL API for frontend.
Alchemy NFT API / Reservoir Protocol — ready APIs for NFT data: media, metadata, ownership, market data. Reservoir additionally aggregates orders from other marketplaces — useful for price discovery.
Orderbook — off-chain storage of signed orders. PostgreSQL with indexing by collection, price, expiration. REST API for frontend. On order cancellation — soft delete from database + on-chain cancel via Seaport for guarantee.
Frontend stack — Next.js + wagmi + viem + RainbowKit (or custom wallet modal). NFT gallery on virtualized list (react-window) for performance with thousands of tokens.
Admin Panel
Collection management: verification (galactic badge), hiding/blocking tokens, featured setup. Transaction monitoring, volume by collections. Fee parameter management. Thin SPA on React with same wagmi stack.
Chains and Multichain
Seaport deployed on Ethereum, Polygon, Arbitrum, Optimism, Base, Avalanche and others. Multichain marketplace — not rewriting contracts, but multichain frontend with correct chain switching and separate subgraph per chain.
| Chain | Gas on listing | Audience | Features |
|---|---|---|---|
| Ethereum | ~$5-30 | High-value collections | Maximum liquidity |
| Polygon | <$0.01 | Gaming, mass market | Low entry barrier |
| Arbitrum | <$0.50 | DeFi-native NFT | Fast transactions |
| Base | <$0.10 | Creator economy | Coinbase ecosystem |
Development Process
Planning (1-2 weeks). Business model, supported chains, feature set, UI wireframes, API schema.
Smart contract level (1-2 weeks). Zone contracts, fee configuration, factory for collections (if needed). Tests in Foundry with Seaport fork-tests.
Indexing (1-2 weeks). Subgraph deployment, orderbook backend, NFT data pipeline via Alchemy.
Frontend (3-5 weeks). Gallery, token pages, listing flow, checkout, user profile, collections. Responsive design.
Admin panel (1-2 weeks). Moderation, analytics, settings.
QA and deployment. Testnet run with real users, load testing API.
Timeline Estimates
MVP marketplace (fixed price, one collection, one chain) — 6-8 weeks. Full-featured white-label (auctions, multichain, mint factory, admin) — 12-20 weeks. Smart contract audit (if custom zone/conduit) — 2-4 weeks on top of development.