Skip to main content
Every launch creates a new fixed-supply token and opens its Uniswap v4 market in the same transaction. The creator does not deposit the paired asset and cannot create more tokens later.

Form fields

Address suffix

Current Base launches use a B20 address ending in 01, and the create page previews it before signing. Current Robinhood, Monad, Arc, BSC and X Layer launches also require an ERC-20 address ending in 01; the app generates it after the final metadata is ready. The suffix identifies the current o1 launch flow. It does not change the token’s permissions, supply, price, or market.

Supply and liquidity

Current launches create a fixed supply of 1 billion (1,000,000,000) tokens. The supply cannot increase after launch. The complete supply is placed into the permanent Uniswap liquidity position when the token launches.

Token implementation

The protocol creates a native B20 token with no administrator. Its 1 billion supply is created once. The creator may optionally retain permission to edit profile information, but cannot mint more tokens or control transfers.Base’s B20 protocol contracts are listed in Production contracts.

Crypto-paired and stock-paired routes

Both routes use the same fixed supply, announcements, fee split and permanent liquidity model. Anti-snipe settings vary by chain: new Arc launches have no surcharge, while Base, Robinhood, Monad, BSC and X Layer retain their 20-second schedule. Base, Robinhood, BSC and X Layer each use one active launch factory for both crypto-paired and stock-paired creation. The selected paired asset determines the market type. See Stock-paired launches for the current Base, Robinhood, BSC and X Layer catalogs.

Optional Dev Buy

The current Base, Robinhood, Monad, Arc, BSC and X Layer launch factories can create the token, seed permanent liquidity, and execute one creator purchase atomically through createLaunchAndBuy. The Include Dev Buy toggle is off by default. When enabled, the creator enters a native ETH amount on Base/Robinhood, MON amount on Monad, native USDC amount on Arc, BNB amount on BSC, or OKB amount on X Layer and reviews the protected minimum output and slippage setting before signing. On Arc, the adapter uses the six-decimal ERC-20 USDC interface to spend the native USDC buy amount from the same underlying balance. There is no wrap or exchange step between the two USDC interfaces. For a cirBTC pair, routing then exchanges ERC-20 USDC for cirBTC before buying from the launch pool. The launch fee and gas are separate from the buy amount. See Arc funding amounts for exact units and approvals. The Dev Buy pays the normal 1% base swap fee but does not pay the anti-snipe surcharge. This exemption applies only to that one atomic creator purchase. Any failure, including output below the protected minimum, reverts the complete launch and buy together. Later purchases follow the pool’s frozen fee schedule. New Arc launches have no surcharge on either the Dev Buy or later trades.

Profile editing

The default profile is permanently immutable. If the creator opts in, the active launch factory lets the current creator update token profile information after launch. The creator can update:
  • token name;
  • token symbol;
  • public profile information, including the image, description, website, X, and Telegram;
  • extra profile information.
This permission cannot create more tokens, change balances, pause transfers, upgrade the token, or remove liquidity.

Creator rights

The active launch factory records the launch-time originalCreator permanently and separately tracks the currentCreator and creatorFeeRecipient. The current creator can propose a two-step creator-rights transfer and can change the destination for future creator-fee credits. If profile editing was enabled at launch, metadata and announcement authorization follow the current creator. Creator rights are not token ownership. They do not grant minting, transfer control, upgrades, balance recovery, or liquidity removal. Already credited fee balances stay with the recipient that earned them. The current application does not expose creator-rights management controls; direct integrations must use the verified active-factory ABI.

Transaction safety

The factory rejects a launch if:
  • the quote is no longer registered;
  • the unique launch identifier was already used;
  • the launch settings changed after the app prepared the transaction;
  • the deadline has passed;
  • the current creation fee or transaction value does not match the active factory configuration;
  • profile or liquidity requirements fail;
  • the token cannot be created exactly as shown;
  • opening the pool would require the creator to supply the paired asset.
The frontend refreshes the launch settings and chain time immediately before submission. If a protected global setting changes while the transaction is pending, the call stops instead of silently using a different configuration. A paired asset’s opening-price refresh intentionally uses the latest registered frame when the launch executes.

Creation result

After confirmation, the app shows the token address and live pool. It also records the paired asset, creation fee, creation route, and market settings from the confirmed transaction. Developers can find exact function and event names in Functions and events. BSC supports crypto-paired and stock-paired creation. Its 0.003 BNB launch fee is separate from gas and any Dev Buy input. See BSC configuration. X Layer uses the same immutable ERC-20 creation flow and a 0.02 OKB launch fee. Quotes include native OKB (18 decimals), USDC (6 decimals), xETH (18 decimals) and 45 wrapped stocks (18 decimals). WOKB is a separate routing wrapper. Ordinary creation needs only the OKB launch fee and gas, with no paired-asset deposit. Optional atomic Dev Buy adds the entered OKB amount to the launch fee. See X Layer configuration.