Guide

Solana Metaplex NFT standards explained

When you mint a profile picture, buy a generative collectible, or list an item on a Solana marketplace, you are almost certainly touching Metaplex standards. Metaplex is not a single program — it is the de facto NFT stack on Solana: the Token Metadata program that attaches name, image URI, and royalty data to SPL mints; optional edition accounts for limited runs; verified collection badges; launch tools like Candy Machine; and newer compressed NFTs (cNFTs) that store ownership in Merkle trees instead of full on-chain token accounts. This guide explains how those pieces fit together so you can read Solscan entries, evaluate mints, and understand how Garden collectibles relate to the same primitives as the wider Solana NFT ecosystem.

What makes an SPL token an NFT?

At the chain level, a Solana NFT is still an SPL token mint with decimals set to 0 and supply capped at 1 (or a small fixed edition count). Ownership is a single token account holding one indivisible unit. Wallets and marketplaces do not guess artwork from the mint alone — they look up a separate metadata account derived from the mint address via Metaplex's Token Metadata program.

That metadata account is a program derived address (PDA) — an on-chain account with no private key, owned by the Token Metadata program, seeded from the mint pubkey. Inside you will find:

  • name and symbol — short strings shown in wallets
  • uri — off-chain JSON (often on Arweave or IPFS) with image, attributes, and description
  • creators — up to five wallet addresses with share weights summing to 100
  • seller_fee_basis_points — royalty rate encoded on-chain (e.g., 500 = 5%)
  • collection — optional parent collection mint and verification flag

The image you see in Phantom is fetched from that JSON URI, not stored in the metadata account itself. That separation keeps rent low but means link rot and malicious URI swaps are real risks — always verify the mint address, not just the thumbnail.

Master editions and print editions

A 1/1 NFT is a mint with supply 1 and no edition machinery. Limited series — "100 prints of this artwork" — use Metaplex edition accounts:

  • Master edition — tied to the original mint; records the maximum print supply (or marks the master as unique with supply 0 prints allowed). The master mint itself is usually the "artist proof" or canonical piece.
  • Print edition mints — separate SPL mints, each supply 1, linked back to the master. Wallets show "Edition 12 of 100" by reading the edition account chain.

Editions matter for provenance and scarcity claims. A random SPL mint with a copied image has no master relationship — marketplaces use edition and collection metadata to filter counterfeits. When you buy a numbered print, confirm on Solscan that the print's edition account points to the expected master mint, not a look-alike.

Metaplex Core (newer asset standard)

Metaplex has shipped Core — a leaner asset model that unifies fungible and non-fungible assets under one program with plugins for royalties and attributes. Most legacy collections still use Token Metadata + SPL mints; Core is the direction for greenfield launches that want lower account count and simpler updates. As a collector, the mental model is the same: on-chain asset record + off-chain URI + optional plugins.

Verified collections

Collections group NFTs under a parent collection mint. The collection authority can verify member NFTs by signing a metadata update — wallets and marketplaces then show a blue-check style badge instead of "unverified."

Verification is a strong signal but not magic. A scam project can create its own collection mint and verify its own fakes. You still need to confirm the collection mint address matches the official project announcement (Discord, website, prior mints). Tools like Tensor and Magic Eden surface verification status; Solscan shows the collection key on the metadata tab.

For generative drops, the collection mint is often created first, then each reveal mint is minted with collection set and verified in a batch after mint — that is why new items may briefly show as unverified during launch hour.

Creator royalties on Solana

Royalties are encoded in metadata as seller_fee_basis_points plus creator shares. Unlike Ethereum's EIP-2981 transfer hooks, Solana has no protocol-level force — marketplaces enforce royalties voluntarily by requiring a royalty payment instruction in the listing transaction. Major marketplaces competed on optional royalties in 2022–2023; today many honor creator fees again, but percentages can differ by platform and whether the seller opts in.

Practical implications:

  • Creators should not assume 100% enforcement — budget for primary sales and brand value, not secondary rent alone.
  • Buyers comparing floor prices should check whether quoted price includes royalty on checkout.
  • Token-2022 transfer hooks can enforce fees at the token layer for new projects — see Token-2022 extensions — but most classic Metaplex NFTs still rely on marketplace policy.

Candy Machine and launch mechanics

Candy Machine is Metaplex's minting protocol for fair launches: a on-chain config account holds supply, price, start time, guard rules (allowlists, token gates, SOL payment), and a hidden or revealed URI base. Buyers pay SOL in a mint transaction; the program creates the SPL mint + metadata in one flow.

Guards are the security surface — weak allowlists, predictable reveal seeds, or misconfigured treasury PDAs have caused exploits. Before minting, read the guard set on explorers or launchpad UIs: payment destination, mint limit per wallet, and whether the collection authority can still freeze or update metadata after mint.

Payment flows resemble any other Solana transaction — recent blockhash, optional priority fees during congestion, and simulation to catch failures before signing. High-demand mints are where RPC reliability matters most.

Compressed NFTs (cNFTs)

Full NFTs cost rent per mint and token account — fine for 10,000 pieces, expensive for millions of event tickets or game items. Compressed NFTs use Solana state compression: ownership leaves are stored in a Merkle tree; only the tree root and a small proof path sit in the transaction. Metaplex's Bubblegum program mints and transfers cNFTs against trees allocated via the Concurrent Merkle Tree program.

Trade-offs collectors should know:

  • Lower cost — minting and transferring cNFTs is dramatically cheaper than classic accounts.
  • Different tooling — not every wallet or marketplace supported cNFTs on day one; check compatibility before buying on a niche launchpad.
  • Indexer dependence — explorers and wallets reconstruct ownership from compression indexers (e.g., DAS API). If the indexer lags, your NFT may not appear instantly.
  • Same metadata model — cNFTs still carry Metaplex-compatible metadata and collection fields; verification semantics align with uncompressed assets.

Gaming platforms, loyalty passes, and large generative drops increasingly choose compression. High-value 1/1 art often stays uncompressed for maximum portability and simplest custody.

Metaplex metadata vs Token-2022 metadata pointer

Classic NFTs: SPL mint + separate Metaplex metadata PDA + optional master edition account. Token-2022 can instead store a metadata pointer extension on the mint itself, pointing at an external metadata account or URI — useful for fungible tokens that need on-mint labels without the full NFT edition stack.

The ecosystems overlap but are not identical. Jupiter and DEX aggregators care about mint program ID and decimals; NFT marketplaces care about Token Metadata layout and collection verification. A project migrating standards may dual-write metadata during transition — always check which program owns the metadata account you are trading against.

Security checklist for collectors

  • Mint address is the identity — bookmark official mints; ignore look-alike images in wallet spam tabs.
  • Read update authority — if the creator can change the URI after sale, they can swap your ape for a rug image. Immutable or revoked update authority is safer.
  • Confirm collection verification against the project's published collection mint, not just a badge in the UI.
  • Simulate before mint — malicious Candy Machine configs exist; use wallet simulation and verify SOL destination.
  • Understand rent — receiving an NFT creates a token account; closing unused accounts later reclaims rent-exempt lamports per the account model.

Key takeaways

  • Metaplex Token Metadata is the standard way Solana NFTs attach name, URI, creators, and royalties to SPL mints via PDAs.
  • Master and print editions encode limited-supply provenance; verify edition links on-chain, not just marketplace labels.
  • Verified collections require the collection authority's signature — confirm the collection mint address against official sources.
  • Royalties are marketplace-enforced on most legacy NFTs; do not treat seller_fee_basis_points as guaranteed income.
  • Compressed NFTs trade full accounts for Merkle proofs — cheaper at scale, with indexer and wallet compatibility caveats.

Related reading