Launching a token

Launch fee

~$5 in the native coin

Opening-bundle fee

~$10, only when bundling

Default supply

1,000,000,000

Liquidity

Full supply, at launch

Default swap fee

1.00%

Dev-buy cap

20% of supply

You need a wallet connected to the launch chain with enough of its native coin for gas and the flat launch fee (0.002 ETH on Robinhood and Base, 0.00685 BNB on BSC, 0 on Arc today), plus whatever you want to spend on an optional dev buy. There is no allowlist, no approval step and no coding. The first time a wallet connects, the app asks you to accept the Terms of Use and Privacy Policy; browsing needs no acceptance, but no launch or trade is submitted while that window is open.

The defaults keep the familiar launchpad shape: 1B supply, a 1% creator-set swap fee paid to you in the chain’s native coin (ETH on Robinhood and Base, BNB on BSC, USDC on Arc). Every one of those is adjustable - see Every launch option - but nothing forces you into the advanced section.

• Chain. Pick the chain first - it decides which options exist on the rest of the form. Live today: Robinhood, BSC, Base, Ethereum, Arc and Solana. Chains marked “coming soon” (Ronin, HyperEVM) can be joined via waitlist but not launched on. The header’s launch menu and /launch?chain=… deep-links land on a chain directly. See Chains & venues.
• Liquidity venue (BSC only). Under the chain tiles, BSC shows a “Liquidity venue” control with the pools the token can be born into: Uniswap V4 (the default - the same audited stack Robinhood, Arc and Base run) or PancakeSwap Infinity (PancakeSwap’s V4-style hooked-pool singleton, where BSC liquidity and the bStocks live). Fees, bundle, dev buy and vanity work identically on both; only the address set the launch goes to differs, and the pick is permanent. Deep-link it with /launch?chain=bsc&venue=v4 or …&venue=infinity. Single-venue chains never show the control. See Liquidity venue.
• Identity. Name, ticker, image, description, and optional links (website, X, Telegram). Name and ticker go on-chain and are permanent - the rest is metadata you can edit later.
• Economics (optional). Total supply, opening market cap, your swap fee, the fee model (pay me, holder rewards or buyback&burn), dev buy, opening bundle, vanity address, and on Robinhood and Base an optional custom LP pair. All immutable after launch.
• Review & deploy. The summary shows the launch fee and, if you bundled wallets, the opening-bundle fee - both read live from the launcher contract you are about to call - plus the dev-buy quote and every setting. One wallet confirmation deploys everything.

In the single launch transaction on a direct-to-pool chain, the launcher contract:

• deploys your token and mints the entire supply to itself - you never hold un-earned supply, and neither does anyone else;
• initialises the hooked pool at your opening market cap and deposits the full supply single-sided just below spot, then burns the LP position to 0xdead - the market exists from this block and nobody can ever withdraw it;
• registers the token with its fee hook, which charges your chosen swap fee on every trade with the platform and referral add-on on top (the pool’s own LP fee is 0);
• records your immutable launch configuration (supply, opening price, fee, fee model, venue) and emits it in public events any indexer can read;
• takes the flat launch fee - and the opening-bundle fee, if any - for the platform treasury;
• executes your optional dev buy, and any bundled wallet buys, as the very first trades in the pool.

The token itself is a deliberately boring ERC-20: fixed supply, no mint function, no pause, no fees inside the token, ownership renounced. On the curve venues the sequence differs in the middle: the launcher initialises a bonding curve instead of a pool (the maths), blocks transfers to the future DEX pool until graduation so nobody can set up a side market while bonding is under way, and lifts that block at graduation.

This table is the one to read twice. “Permanent” means no admin, creator or upgrade path can change it for a launched token.

Any native coin you send beyond the launch fee (and the opening-bundle fee, if you bundle) is spent buying your own token inside the launch transaction. Because it is atomic, no sniper can land a buy between your launch and your first purchase - the block in which your token becomes tradable is the block in which you already bought.

• Capped at 20% of supply on-chain (the launch form's own slider stops slightly lower, at 19%). The form's presets (25/50/75/Max) are fractions of that cap; a buy that would exceed the on-chain cap makes the whole launch revert rather than silently buying less.
• It is a normal buy into the pool: the standard swap fee applies, and it moves the price like any other buy.
• It is slippage-guarded with a minimum-tokens-out derived from a live quote at submit time.
• It is fully public - the launch event carries the dev-buy amounts, and the token page shows them.

Text and images do not belong on-chain, but they should not be forgeable either. The launch transaction commits a hash of your metadata; after the transaction confirms, the app uploads the description, image and links to the API, which verifies them against that hash before accepting. If the upload fails (a dropped connection, say), the app retries and self-heals - your token is never stuck without its identity.

Images are limited to 5 MB and converted to WebP for serving. The creator can edit description and socials later from the token page; name and ticker, as above, never change. The exact hashing rule - so a partner can re-derive the commitment independently - is published in the API's metadata commitment section.

• Your token appears in the multichain board within about a second, with its chain mark and venue chip (“V4”, “Infinity”, “PONS”), and gets its own page at /token/<address>.
• On the direct-to-pool chains it is tradable immediately: anyone can buy and sell in its pool from the token page, and price charts work from the first trade. On a curve venue it starts in the Bonding state instead, and the page shows a live “% to graduation” meter.
• The contract source is verified automatically on Sourcify and the chain’s explorer, so aggregators show the “verified” and “renounced” badges without you doing anything.
• Your fee share starts accruing from the very first trade - including your own dev buy - and is claimable at any time from the token page (or, on a holder-reward or buyback&burn token, the keeper puts it to work every cycle).
• If people you referred trade it - or anything else - you also earn the referral rail on their volume.