This page describes the web create form. Launching through X has a narrower feature set and different profile-editing defaults. See the o1 Bot V1 guide and X command reference.
Choose a launch product
On Base, Robinhood, BSC, Monad, X Layer and Arc, choose Standard for the standard fee-sharing model or Tax to set buy and sell taxes, creator funds, holder dividends and burns. Tax also lets you choose a minimum holding for dividends and optional anti-sniping. Use the sliders or enter percentages with up to six decimal places. Each chain uses its own factory and paired assets. See the launch settings for all six Tax suites. Read Tax tokens before choosing those settings. They do not change an existing Standard launch. On Base and Robinhood, $O launches pair a new ERC-20 with wstO. It has no creation fee, allocation controls or anti-sniping option. The review shows the Factory’s buy/sell burn rates, which become fixed for that pool. See $O launches. The shared identity and profile fields below apply to all three products.Form fields
Address suffix
Current Base Standard launches use a B20 address ending in01, and the create page previews it before signing. Base Tax, Base $O and current Robinhood, Monad, Arc, BSC and X Layer launches 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
- Base Standard B20
- Other Standard ERC-20
- Tax ERC-20
- $O ERC-20
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
Crypto-paired and stock-paired launches share the same fixed supply and permanent liquidity model. The selected paired asset determines the market and payout currency. Tax settings work the same way for both kinds of pair. Standard anti-sniping varies by chain; Tax on Base, Robinhood, BSC, Monad, X Layer and Arc lets the creator choose whether to enable it.
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 throughcreateLaunchAndBuy. 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 pool’s ordinary fee: the configured Standard base fee or the creator-selected Tax buy total. It 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 Standard launches have no surcharge on either the Dev Buy or later trades.
For $O launches on Base and Robinhood, the website uses ETH. The route acquires $O through USDC on Base or USDG on Robinhood, deposits it into that chain’s wstO vault, then buys the new token. The normal wstO buy burn applies; there is no surcharge to exempt. You need no wstO approval, and transaction value is the entered ETH amount with gas additional. Plain creation has zero transaction value. All conversion legs and the purchase must succeed together. The Public API and direct contract integrations also support held wstO. See $O launch integration.
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.
Creator rights
The active launch factory records the launch-timeoriginalCreator permanently and separately tracks the currentCreator. Standard and Tax additionally track a creatorFeeRecipient, which can be changed for future creator-fee credits. The current creator can propose a two-step creator-rights transfer. Announcement authority follows the current creator. Metadata editing also follows that creator when profile editing was enabled at launch. $O launches retain these project rights without a creator-fee recipient or fee claims.
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.