Create a collection

Create lets you configure and save a collection before it is live. Download a draft as a backup. Saving a draft or uploading a banner does not deploy contracts. Only allowlisted creator wallets can launch; membership invitations do not grant this permission.

The launch review uses your signing wallet as creator. It checks the deployed factory, fee-model version, metadata, fees and current price conversion. The review expires after two minutes. A native launch deposits the entire supply into single-sided liquidity and initially leaves trading closed.

1. Set the name, symbol, supply, tokens per NFT and starting price.
2. Prepare final metadata and collection images.
3. Configure fees, royalty recipient, sniper protection and any buyback strategy.
4. Review exact settings and gas, then deploy from your approved Chimera wallet.
5. Keep the transaction hash. Fund the reveal reserve before opening trading on the collection page.

Do not submit a second deployment while the first transaction is pending. Use its transaction hash to recover confirmation.

The default is 1,000,000,000 tokens, with 1,000,000 tokens backing each NFT. At $0.000005 per token the starting FDV is $5,000 and the initial backing value is $5 per NFT. Changing supply, backing units or price changes these figures.

USD input is converted to WETH using a current quote during review. The pool price rounds to a usable tick. Starting FDV is a valuation, not deposited liquidity. The first actual NFT-sized purchase can cost more because of fees and movement along the liquidity curve.

Use a square collection logo and a wide banner, ideally 1600 × 600. PNG, JPG, WebP and animated GIF uploads are supported up to 20 MB each. These profile images are separate from the NFT metadata and artwork hosted on IPFS. Add optional website, X, Discord and Telegram links for the collection page.

Prepare an unrevealed metadata URI and the final revealed metadata base URI. Revealed metadata files use four-digit names beginning with 0001.json. Check that each file resolves and references the intended artwork. A folder commitment records what was committed; it does not provide hosting by itself.

If no explicit commitment is supplied, the launch flow hashes the revealed folder URI. Verify the final folder before deployment. Broken metadata paths cannot be fixed by refreshing the marketplace.

Native launch supply goes into dedicated liquidity custody, not the creator’s wallet. The pool starts with the token side only, and purchases bring in WETH. The original launch position is locked without a creator withdrawal path and does not participate in external LP reward allocations.

The base pool LP fee is zero. Chimera’s hook provides the configurable WETH fee accounting. Concentrated liquidity and price ticks still affect execution; zero LP fee does not mean zero trading fee or unlimited liquidity.

Every normal canonical trade includes a 1% base hook fee, paid in WETH and split as below. Quotrons support is part of this base allocation for every launch, rather than an optional 0.5% surcharge.

Creators may allocate up to another 9% across activated NFT rewards, eligible external LPs, custom recipients and buybacks. The maximum normal configured fee is 10%. Additional creator compensation can be configured as a custom destination. External LP fees are charged only while eligible external liquidity is active.

Creators can change configurable rates within the cap. The base split remains fixed in the hook’s accounting design. Existing proxy governance retains upgrade powers; see the contract and security section.

100 basis points (bps) = 1%. NFT sale royalties and gas are separate.

When enabled, opening trading starts five one-minute fee stages: 60%, 50%, 40%, 30% and 20%. These replace the normal hook fee, then the normal fee resumes after five minutes. Extra protection fees follow the active fee-recipient proportions.

Contract-configured eligible holders can pay the normal rate, but the current launch UI does not expose eligibility-rule setup. Registered same-pool buybacks are fee-exempt even during protection. Opening trading is permanent and starts the clock immediately.

The royalty schedule includes 0.25% for Chimera plus a creator-selected royalty from 0% to 9.75%. A 5% creator royalty therefore means 5.25% total. Choose the creator’s receiving wallet or contract before deployment. Marketplace fees and token hook fees are separate.

An immutable royalty splitter reserves the platform share of royalty receipts. Ink launches use the configured OpenSea transfer validator for compatible enforced sale flows. ERC-2981 reporting alone cannot force a payment; transfer validation and marketplace order compatibility matter. A transfer does not reveal an unrelated off-market payment.

The collection’s reveal reserve pays Pyth request fees in ETH. Fund it from the collection page before opening trading, and monitor it as purchases materialize NFTs. The required fee can change; the interface reads the current provider quote. Reveal deposits cannot be withdrawn.

A worker processes pending reveal work and retries ready deliveries. The oracle determines the random result; the worker does not choose artwork. A delayed worker or underfunded reserve can delay reveal without requiring the holder to activate the NFT.

The NFT reward allocation funds rewards for activated NFTs. Token-backed but unactivated NFTs do not earn it. A custom fee destination can implement a different payout mechanism, but that behavior comes from the destination contract, not from the default WETH reward ledger.

For lifecycle, claims and transferred rewards, open the Rewards topic. No allocation guarantees trading volume or a fixed return.

Set a buyback rate within the extra 9% budget. Choose a token recipient or permanent burn, the executor address and the minimum WETH threshold. These strategy settings are fixed at launch; its fee rate remains configurable under the normal cap.

The executor defaults to the creator wallet. Reaching the threshold makes an execution eligible, but does not send a transaction automatically. Read the Buybacks topic before selecting a keeper or recipient contract.