How MNTD works

1. 01

   Discover a launch

   Browse tokens and their associated NFT collections from Explore.

2. 02

   Review the details

   Check the artwork, market activity, contract addresses and pairing information.

3. 03

   Connect your wallet

   Connect on Ethereum when you are ready to interact with a market.

Understand the pairing

A token and its associated NFT collection are shown together on the market page. Review that market’s specific rules before taking an action.

Use Connect wallet in the header and choose your wallet provider. Check the site address and wallet connection request before approving it.

This launchpad uses Ethereum. A wallet connection is separate from a transaction signature and does not itself transfer funds. If your wallet is on another network, use the network control to switch to Ethereum.

Launching and trading are closed in this preview. Connecting a wallet does not enable execution or make a demo market real.

Browse launches and their paired NFT collections from Explore. Use the search and sort controls to find a market, then inspect its artwork, pairing information, price history and contract references.

Demo markets use illustrative data and cannot execute trades. Collection artwork does not imply affiliation, reserve ownership or a live deployment.

The collection is the reference point for a separate reserve contract. In the collection-paired flow, a new coin has two Uniswap v4 markets: coin / ETH and coin / collection reserve units. The NFT artwork identifies the collection; it is not the asset deposited directly into the coin’s liquidity pool.

Your coinERC20 launch token

ETH poolCoin / ETH

Collection poolCoin / reserve units

Collection artwork is illustrative. Inclusion does not imply affiliation, ownership, an endorsement, or an active market.

The launch coin and reserve units are different tokens. Holding the launch coin does not itself grant an NFT, fractional NFT ownership, or a fixed redemption value. A holder would first need reserve units, an executable route, and the reserve’s applicable conditions to use a reserve exit.

• Review the token name, symbol, supply and allocation.
• Confirm the collection address and applicable reserve configuration.
• Check opening valuation, pool allocation, fees and recipients.
• Inspect the exact contracts, permissions and source verification.
• Review irreversible actions and the wallet transaction before signing.

The preview is not a deployment. Fresh contract wiring, fee policy and launch rehearsal remain outstanding. No launch is completed until a valid transaction receipt confirms it.

1. 01

   Name your coin

   Set the project identity and optional artwork. The form keeps the live preview alongside your choices.

2. 02

   Select the collection

   Choose a collection supported by the reserve configuration. Selecting it does not transfer an NFT or make the coin an official collection project.

3. 03

   Review the market

   Check token configuration, pool allocation, opening valuation, fees, and irreversible actions. A preview is not a deployment.

4. 04

   Confirm in your wallet

   When launching is enabled, the wallet signs the transaction. The interface must wait for a confirmed receipt before reporting a completed launch.

The standard candidate token uses a fixed 1 billion token supply. The collection-paired path allocates half to each initial pool. These are properties of the standard flow; custom contract paths and future deployments need their own verification.

The candidate CollectionReserve accepts ETH and issues reserve units. Its deposit accounting mints one raw unit per wei; with 18 decimals, depositing 1 ETH mints 1 displayed reserve unit. This deposit ratio is not a guaranteed market price or a guarantee that every unit can always exit for ETH.

NFT acquisition is conditional

The reserve can purchase NFTs through approved marketplace adapters when it has enough spendable ETH, an acceptable listing, a fresh posted floor, and an executable transfer. Purchases must leave the configured cash floor intact. The source also caps NFT intake per time window. A new market does not imply the reserve already owns any NFTs.

Reserve exits are not coin redemption rights

• ETH exit: reserve units can be burned for ETH at the contract’s deposit ratio only while cash is available, first come, first served.
• NFT exit: the candidate supports redeeming reserve units for available NFTs at the reserve’s ask, with a maximum-spend check. That ask can exceed the posted floor and depends on acquisition cost.
• Direct purchase: an available reserve NFT can be bought with ETH. Successful execution still depends on inventory, price, and collection transfer rules.

The admin key matters

The reserve owner controls its oracle and approved adapters. In the candidate code, the owner can pause NFT intake and, once paused, rescue NFTs to another address. The first rescue retires that reserve’s NFT intake. The owner has no general ETH-withdraw function, but its power over the NFT inventory remains material.

The launch flow derives starting prices from an opening valuation and oracle inputs. The candidate hook can route part of an ETH-pool swap through its associated collection pool. This is contract routing logic; it does not fix the coin’s price to the NFT floor, remove arbitrage, or guarantee that both pools can fill a trade.

After launch, executable quotes depend on pool state, available liquidity, fees, slippage, and the route. An NFT floor is a posted reference input, not a promise that an NFT can be sold at that price. The launch coin can lose all its value.

The candidate launch flow sends its initial v4 position NFTs to LiquidityLocker. That contract has no general transfer or principal-withdrawal path. A fresh deployment must match the reviewed source and wiring before its positions can be described as permanently locked.

The lock’s scope is the initial launch positions. Other liquidity providers may own removable positions. A locked position is not a price floor and does not guarantee an exit, a minimum price, or sufficient liquidity.

Hook fee collection is a separate path. Collecting accrued hook fees does not require ownership of the liquidity position and does not remove the pool’s principal.

The preview uses configuration defaults. They are not a verified live fee policy. The candidate fee hook takes a fee on the quote side of a swap. Its launch pools use zero LP fee; that does not make the trade free.

Preview trade fee

1%

Candidate hook cap

5% per pool

Preview creator allocation

0% of the fee

Launch fee

Not verified · plus gas

The fee admin can override pool rates within the hook’s cap. The candidate hook accrues claim balances, then permits collection to its configured locker / fee splitter. Recipients and allocation must be checked for the specific deployment; this guide does not promise creator revenue or holder yield.

Gas, approvals, price impact, and slippage are separate from the trading fee. A rejected or reverted transaction can still consume gas if it was submitted on chain.

The standard token source has no post-launch mint, owner, pause, or token-level transfer tax. The factory also contains custom-token launch and screening paths whose availability depends on deployment configuration. Those paths must be assessed separately from the standard token.

Bytecode screening identifies certain patterns. It is not an audit and cannot establish that a token is safe. Review the exact token contract, allocations, owner permissions, and other contracts involved in a launch.

• Prices and liquidity can disappear.

  Tokens and NFTs can lose all their value. Thin liquidity, concentrated ranges, and slippage can make an exit costly or unavailable.

• Trusted keys have real permissions.

  Reserve admins control NFT intake, adapters, and emergency NFT rescue. Oracle keys post floors. Fee admins can change rates within the cap.

• Cash and inventory are finite.

  ETH redemptions depend on available reserve cash. NFT exits depend on inventory, the ask, transfer rules, and transaction execution.

• Source code is not a deployment guarantee.

  No independent audit is supplied with this preview. Contract correctness, wiring, integrations, and launch execution need verification. Wallet signatures and on-chain transactions can be irreversible.

MNTD launch contracts are not connected to this preview. Existing Uniswap infrastructure is listed separately; its presence does not mean a MNTD market has been deployed. Network: Ethereum, chain ID 1.

Collection imagery belongs to its respective creators. Terms of Use · Privacy Policy