A Solana NFT marketplace is a set of on-chain programs plus an indexer and front end that list, buy and bid on NFTs issued under Metaplex standards. The decision that shapes everything else is which asset types you support: legacy Token Metadata NFTs, programmable NFTs, Metaplex Core assets or compressed NFTs. Each one is stored and transferred differently.
This page focuses on those architectural choices. For a step-by-step build and feature checklist, see the companion guide on Solana NFT marketplace development.
How Solana NFTs differ from Ethereum NFTs
Solana programs are stateless; data lives in separate accounts. A classic Solana NFT is not an entry in a contract mapping but a set of accounts: an SPL token mint with supply one and zero decimals, a token account holding it for the owner, a metadata account and a master edition account created by the Metaplex Token Metadata program. Marketplaces therefore deal with account derivation (program-derived addresses), rent-exempt deposits and transaction size limits, not with approve calls.
The four asset types
| Standard | Structure | Royalties | Mint cost | Marketplace considerations |
|---|---|---|---|---|
| Token Metadata (legacy) | SPL mint + token account + metadata + edition accounts | Not enforced | Highest (several accounts' rent) | Most existing collections; widest support |
| Programmable NFTs (pNFTs) | Token Metadata with frozen token accounts and rule sets | Enforceable via rule sets | High | Transfers must go through Token Metadata instructions; more compute |
| Metaplex Core | Single account per asset, plugin system | Enforceable via royalties plugin | Low | The current default for new collections |
| Compressed NFTs (Bubblegum) | Leaf in a concurrent Merkle tree; data in ledger history | Recorded, not enforced | Tiny per asset | Needs DAS API and Merkle proofs for every transfer |
The Metaplex developer documentation covers each program in detail. A credible marketplace in 2026 should support at least legacy, pNFT and Core; compressed NFT support matters if you target games, loyalty programs or large airdrops.
Compressed NFTs in practice
Compression stores only a Merkle root on-chain. To transfer a compressed NFT, your program must supply a proof against the current root, fetched from an indexer that implements the Digital Asset Standard (DAS) API. If the indexer is down or lagging, trading stops. Large proofs also eat into Solana's transaction size limit, so marketplaces use canopy depth on the tree and address lookup tables to fit.
Marketplace program design
- Listings. Common designs either escrow the NFT in a program-owned account or keep it in the seller's wallet with the marketplace program as delegate. Delegate-based listings let NFTs remain visible in the seller's wallet but require handling cases where the delegation is revoked.
- Bids. Collection-wide bids hold SOL in a program-derived escrow account; filling a bid transfers any qualifying NFT and releases the funds.
- AMM pools. Solana's low fees made on-chain NFT pools practical; Tensor popularized pool-based trading.
- Royalties. For pNFTs and Core, the asset's rules decide; for legacy NFTs, royalty payment is a marketplace policy choice.
- Framework. Most teams write programs in Rust with Anchor, which handles account validation boilerplate that is otherwise a common source of bugs.
Off-chain infrastructure
Real-time Solana indexing is demanding because of the chain's throughput. Options include RPC providers with DAS and webhook support, Geyser plugin streams from your own node, or both. Expect to cache metadata and images aggressively; Arweave via Irys is the common storage for Solana metadata.
Transactions need priority fees during busy periods and should set compute unit limits explicitly. Retries and blockhash expiry handling are essential for a smooth buying experience.
Build sequence
- Decide which asset standards you support at launch.
- Write listing, bid and settlement programs in Anchor; test on a local validator and devnet.
- Integrate DAS-capable indexing and webhooks.
- Connect wallets through the Solana wallet adapter (Phantom, Solflare, Backpack and others).
- Implement priority fees and transaction retry logic.
- Commission an audit focused on account validation, signer checks and PDA seeds.
Honest context
Solana suffered several network outages in 2022 and 2023, which hurt NFT trading at the time; stability has improved markedly since. Solana's NFT market is well served by established marketplaces, and much speculative activity on the chain has shifted to memecoins. A new marketplace needs a niche: a game, a brand's collections, compressed-NFT loyalty programs, or a specific community. For context on alternatives, compare BNB Smart Chain and Ethereum L2s, or see general NFT marketplace development.
Frequently asked questions
Should a new Solana collection use Core or legacy Token Metadata?
For most new collections, Metaplex Core: it is cheaper, simpler and supports enforced royalties. Legacy remains necessary to support older collections.
Are royalties enforced on Solana?
For pNFTs and Core assets with royalty rules, yes, at the program level. For legacy NFTs, it depends on the marketplace.
What are compressed NFTs good for?
Large volumes of low-value assets: game items, tickets, loyalty badges and airdrops, where minting millions of regular NFTs would cost too much.
Which language are Solana marketplace programs written in?
Rust, usually with the Anchor framework. Front ends use TypeScript with Solana's web3 libraries and Metaplex's Umi tooling.