An NFT exchange is a marketplace built around trading rather than browsing: it focuses on making NFTs easy to buy and sell quickly through collection-wide bids, liquidity pools, swaps and fast settlement. The core engineering problem is liquidity for assets that are, by definition, not interchangeable.
If you want a storefront where creators list and collectors browse, start with NFT marketplace development. This page is about the trading layer.
Why NFTs are hard to trade
A fungible token has one price. An NFT collection of 10,000 items has 10,000 slightly different assets, many of which have never traded. That makes order books thin and price discovery slow. Every design below is a way around that: treat items as partly interchangeable, so liquidity can concentrate.
Four trading mechanisms
| Mechanism | How it works | Strength | Weakness |
|---|---|---|---|
| Signed order book | Sellers sign listings off-chain (EIP-712); buyers fill on-chain. Seaport is the common protocol. | No gas to list; flexible terms | Liquidity depends on active makers |
| Collection and trait bids | A buyer offers a price for any token in a collection, or any with a given trait | Gives sellers instant exits at the bid | Bidders need capital parked; spoofing risk |
| AMM pools | Pools hold NFTs and ETH and price along a bonding curve (the sudoswap model) | Always-on liquidity, programmatic | Treats all items as floor; LPs bear inventory risk |
| Vault tokens | NFTs deposited into a vault mint fungible tokens that trade on a DEX (the NFTX model) | Uses deep ERC-20 liquidity | Only works for floor-quality items |
Most serious exchanges combine the first two and integrate the others through routing. Blur showed how much trading volume collection bids can attract, though much of it was driven by token incentives.
How an NFT AMM prices
In a sudoswap-style pool, the pool creator sets a spot price and a curve. With a linear curve, each sale out of the pool raises the price by a fixed delta and each purchase into it lowers the price by the same delta. With an exponential curve the change is a percentage. A two-sided pool earns a fee on the spread. This is simpler than an x·y=k pool because NFTs are not divisible, so the curve steps one item at a time.
Exchange components
- Settlement contracts. Use an audited protocol such as Seaport rather than writing your own order-matching contract. Custom matching logic is a frequent source of exploits.
- Order and bid service. Stores signed orders, validates them against on-chain state (owner, approval, nonce), and removes stale ones. Stale orders that fail on fill are the most common user complaint.
- Indexer. Tracks transfers, sales, approvals and metadata across chains in near real time. Many teams use a commercial NFT API for this; see NFT API providers.
- Routing. Sweeping five items might mean buying from your book, another marketplace and an AMM pool in one transaction. That is aggregator territory; see aggregator development.
- Pricing data. Floor, trait floors, last sale and bid depth. Be careful: thin collections are easy to manipulate.
- Wallet layer. Browser wallets for traders; embedded wallets for newcomers.
Custody: the big decision
A non-custodial exchange never holds user assets; trades settle wallet-to-wallet through contracts. That keeps you out of most custody regulation and removes a honeypot. A custodial exchange, where users deposit NFTs into platform wallets and trade on an internal ledger, can offer instant trades and fiat rails, but you take on custody risk, security obligations and likely licensing. In the EU, MiCA mostly excludes unique NFTs, but fractionalized or series NFTs that behave like fungible tokens can fall within scope.
Security priorities
- Never ask users to sign broad approvals to an unaudited contract.
- Show human-readable signing prompts so users know what an order commits them to.
- Support on-chain cancellation and bulk nonce increments, so users can invalidate all old orders after a compromise.
- Detect wash trading before it pollutes rankings and reward programs.
- Get settlement and pool contracts audited; see smart contract audits.
Build process
- Choose chains and the collections you will support at launch. Liquidity is the product, so start narrow.
- Integrate an existing settlement protocol and an indexer.
- Ship listing, buying and collection bids first. Add trait bids and pools later.
- Build bid and order validation services with monitoring for failed fills.
- Run an audit on any custom contracts and a penetration test on the backend.
- Launch with market makers or committed traders, not with token incentives alone.
A realistic first version with an experienced team of four to six engineers takes roughly three to five months, mostly spent on indexing, order validation and UX rather than contracts. Incentive programs are cheap to code and expensive to run; trading driven only by rewards tends to vanish when rewards end.
Frequently asked questions
What is the difference between an NFT exchange and an NFT marketplace?
The terms overlap. "Exchange" usually signals a trading-first product with bids, pools and fast execution; "marketplace" suggests listings and discovery. Many products do both.
Can NFTs be traded on an AMM?
Yes. Pools that price along a bonding curve, or vaults that turn floor NFTs into fungible tokens, give always-on liquidity, but they treat items as interchangeable, so rare items are underpriced.
Do I need my own token for an NFT exchange?
No. Tokens have been used to bootstrap volume, but they add regulatory questions and the volume often leaves when emissions drop. A fee-based model is simpler.
Which token standards should an NFT exchange support?
ERC-721 and ERC-1155 on EVM chains at minimum. Supporting Solana or Bitcoin Ordinals means separate settlement logic for each.