An NFT metaverse launchpad is a platform where virtual-world projects sell their first NFTs: land parcels, avatars, wearables and in-world items. This guide explains the contracts, sale types, money flow and project checks such a platform needs, so you can scope a build or judge a vendor's plan.
This page covers a launchpad on one blockchain, and a separate guide covers metaverse launchpad development across several chains, with shared allowlists, per-chain contracts and cross-chain messaging.
How an NFT metaverse launchpad differs from a general launchpad
Every launchpad sells newly minted NFTs for a project and keeps a fee. A metaverse launchpad has three extra jobs, because the assets must work inside a game or 3D world.
- Land needs coordinates. Each token ID maps to a parcel with an x and y position and sometimes a size, and the sale page needs a map, so buyers can pick a parcel or receive a random one.
- Items need usable 3D files. Wearables and avatars ship with models that the target world can load. glTF (and its binary form GLB) is the common exchange format, and VRM is an avatar format built on glTF 2.0. Each item also needs a thumbnail and the attributes the game reads.
- Promised uses need a record. Buyers expect an asset to do something in the world, such as unlock an area or a game feature, so the launchpad should store what the project promised and the delivery date for each promise.
Sale types and how the contracts handle them
| Sale type | How the contract works | Typical use |
|---|---|---|
| Allowlist presale | The contract stores a Merkle root, one short value that represents the whole list of eligible addresses, and each buyer submits a proof that their address is in the list. Storing one root costs far less gas than storing every address. | Early community members |
| Fixed-price public mint | The contract enforces a price, a cap per wallet, a total supply cap, and start and end times. | Wearables and avatar editions |
| Dutch auction | The price falls on a schedule until the drop sells out. Some contracts refund early buyers who paid more than the final price. | Scarce land, where the project does not know the right price |
| Raffle | Users enter during a window, and a random number from a service such as Chainlink VRF picks the winners. | High-demand drops, where buyers would otherwise pay ever higher gas fees to mint first |
| Parcel selection | The buyer names a token ID, and the contract checks that the parcel is free and charges the price for its tier. | Premium land near landmarks |
The current version of Chainlink VRF is v2.5. A project can pay for random numbers through a prepaid subscription or per request, in LINK, Chainlink's own token, or in the chain's native token.
Contract layout
A common design uses a factory contract that deploys one collection per project and one sale contract per drop. Land and unique avatars use ERC-721, because each token is unique. Wearables sold in editions use ERC-1155, because one token ID can have many copies.
Keeping sale logic out of the token contract lets you reuse audited sale modules for every drop, and the token contract then only handles ownership, transfers and metadata.
Drops with hidden traits use a delayed reveal. Tokens mint with placeholder metadata, and the project sets the real metadata location after the sale ends. The project should publish a hash of the final metadata before the sale, so that after the reveal buyers can compare the real metadata with it. A match shows that the project did not reassign rare items to wallets of its own choice after the sale.
Funds, fees and royalties
A launchpad holds buyers' money between the sale and the payout to the project, so the code that holds and pays out this money carries the most risk on the platform. These rules reduce that risk:
- Keep sale proceeds in escrow in the sale contract, and release them to the project in stages tied to milestones, or at least after a short delay.
- Take the platform fee on-chain at withdrawal, so anyone can check the amount.
- Set royalty information on each collection with EIP-2981. The standard only reports a royalty amount, and each secondary marketplace decides whether to pay it, and several large marketplaces make royalties optional.
- Write a refund path for a sale that does not reach its minimum.
Many metaverse projects also sell a fungible game token next to their NFTs. A token sale is a different product with different legal exposure, and the IGO launchpad guide covers game-token offerings.
Project vetting
The 2021 to 2022 metaverse boom produced many land sales for worlds that were never finished, and buyers of those parcels lost most of their money. A CoinGecko study reported in mid-2024 that average land prices in The Sandbox and Decentraland had fallen about 95% and 89% from their peaks. DappRadar counted about $6.5 million in metaverse NFT trading for all of August 2025, a small amount next to the boom years.
A metaverse launchpad can check each project before a sale with these steps:
- Require a playable build, not just a trailer, before any land or item sale.
- Identify the team through KYC with the launchpad, even if the team stays anonymous to the public.
- Load every asset file in the game client, and check polygon counts and texture sizes against the limits of the game engine.
- Review the contracts for admin powers, such as whether the project can mint extra land, change metadata or pause transfers.
- Release funds by milestone when a project sells items for features it has not built yet.
Regulation
NFT rules depend on what the token promises. In the United States, the SEC closed its investigation of OpenSea in February 2025 without enforcement action, but the closed investigation did not create a general rule for NFTs. A drop that promises buyers a share of revenue or a price increase can still look like a securities offering.
In the European Union, the Markets in Crypto-Assets Regulation (MiCA) excludes unique, non-fungible tokens. MiCA opens with explanatory notes called recitals, and Recital 11 says that a large series or collection of tokens may be a sign that the tokens are fungible, which brings them under MiCA. A launchpad that sells large edition drops in the EU should get a legal opinion on whether MiCA applies. In most countries, launchpads also run KYC checks on project teams and screen buyers against sanctions lists.
Build process
- Define the asset types and the target engine or world. Options include Unity, Unreal, web engines such as three.js or Babylon.js, or the SDK of an existing world.
- Write the collection factory and sale modules, then have them audited. The smart contract audit guide explains how to scope an audit.
- Build the project dashboard, where projects upload assets, set supply and prices, load allowlists and schedule drops.
- Build the buyer side: drop pages, parcel maps, 3D previews, wallet checkout and card checkout.
- Add an indexer, such as a subgraph or an indexing API, which shows ownership to the game's servers and to buyers within seconds of each mint.
- Run a pilot drop with one vetted project, and open applications to other projects after the pilot.
Team, timeline and cost drivers
The figures in this section are estimates, not quotes. A first version with a collection factory, allowlist, fixed-price and Dutch auction sales, a project dashboard and 3D previews needs four to six people. A typical team has two contract engineers, two frontend engineers, one backend engineer and part-time 3D and design help, and needs about three to five months, plus time for the audit.
These features add time and cost:
- Interactive land maps with parcel selection
- Raffles that use verifiable randomness
- Card checkout through a fiat payment provider
- In-world integration for each partner project
- Support for a second chain
The NFT launchpad development guide covers launchpads for other kinds of collections, and the metaverse NFT marketplace guide covers resale after the drop.
Frequently asked questions
What is an NFT metaverse launchpad?
An NFT metaverse launchpad is a platform where virtual-world projects run their first NFT sales of land, avatars, wearables and items. The platform handles minting, payment, allowlists and reveals, and it checks that the assets work in the target world.
How is a metaverse launchpad different from a regular NFT launchpad?
The contracts are similar, but a metaverse launchpad adds a 3D asset pipeline, land coordinates, in-world attributes and a link to the world's servers. Project checks also matter more there, because the asset's value depends on a game that may not be finished.
Should land be ERC-721 or ERC-1155?
Land should use ERC-721, because each parcel is unique and tied to coordinates. ERC-1155 suits wearables and items sold in editions.
How do I stop bots from buying an entire drop?
Use allowlists, per-wallet caps and raffles instead of first-come sales. You can also use signature-based minting, where your backend signs each permitted mint after a bot check.
Is there still demand for metaverse NFT drops?
Demand is far smaller than in 2021 and 2022, and most of what remains comes from games with active players. A launchpad can work as a service for vetted game studios, but speculative land sales have little demand.