How it works

The complete o1 Launchpad lifecycle from setup and token creation to trading, fee claims, announcements, and staking.

Creators use the o1 interface to configure a token and approve the launch transaction in their wallet. The launch contracts create the token and its Uniswap market together. The creator pays the current global native creation fee plus network gas. The blockchain is the source of truth, while o1 organizes confirmed public data so launches, trades, fees, holders, and announcements are easy to view.

End-to-end lifecycle

1. Configure the launch

   The creator supplies a name, symbol, image, paired asset, optional links and description, and a profile-editing preference.

2. Review the launch

   The o1 confirmation screen presents the paired asset, fixed supply, permanent liquidity, current creation fee, profile permission, and the predicted address when available.

3. Prepare current settings

   After the creator confirms the review, the app stores the token image and public profile on IPFS, includes that metadata link in the launch request, and refreshes the selected paired asset, creation fee, supply, liquidity settings, and current chain time.

4. Sign the launch

   The creator approves the launch transaction and pays the displayed creation fee plus the chain’s network gas. Base and Robinhood currently use one 0.001 ETH fee for both crypto-paired and stock-paired launches. Monad charges 100 MON, Arc charges 2 native USDC, BSC charges 0.003 BNB, and X Layer charges 0.02 OKB.

5. Create the token

   On Base, the protocol creates a native B20 token with no administrator. On Robinhood, Monad, Arc, BSC and X Layer, o1 creates a fixed-supply ERC-20 with no owner or additional minting function. The fixed 1 billion supply is created once.

6. Open permanent liquidity

   The launch contracts open the Uniswap v4 pool at the configured starting price and place the complete fixed supply into permanent liquidity.

7. Optionally execute the Dev Buy

   When the creator explicitly enables it, the Base, Robinhood, Monad, Arc, BSC or X Layer launch contracts execute one protected native-funded purchase in the same transaction. The toggle is off by default, and a failed purchase reverts the complete launch.

8. Open the launch page

   After confirmation, the launch page shows the token profile, live market, trading interface, trades, holders, and announcements.

9. Optionally use staking

   Wallet-held tokens may be deposited into a separate compatible staking vault. A launch does not create a vault automatically, and vault creation remains an independent permissionless transaction.

Where each asset lives

Asset	Location	Who can move it
Tradable token supply	The permanent Uniswap liquidity position	The launch contracts prevent its removal
Staked wallet tokens	The separate staking contract	The participant can withdraw principal according to the selected vault’s fixed policy
Creation fee	Paid to the configured fee recipient in the launch transaction	The creator’s wallet pays the exact live fee shown before signing
Accrued swap fees	A dedicated claimable balance for each recipient	Creator, platform, or valid referrer according to the fee split
User trade funds	The user’s wallet and the Uniswap pool during the trade	The transaction approved by the user

Swap lifecycle

1. Review the trade

   The interface shows the input amount, estimated output, minimum received, price impact, current fee, slippage limit, and estimated network fee. It automatically applies a 10-minute transaction deadline.

2. Sign with the wallet

   The wallet submits a trade for the amount the user chose to spend or sell.

3. Apply pool and fee logic

   Uniswap calculates the result, and the launch contract applies the swap fee in the pool’s paired asset. A stock-paired market therefore charges its fee in that Stock Token.

4. Settle the swap

   The user receives the purchased or sold asset. Creator, platform, and valid referrer fee balances become claimable independently.

Trading begins immediately. o1 uses input-amount swaps for both buys and sells: the trader chooses how much to spend or sell, and the interface protects the minimum amount received with a slippage limit. These swaps remain available while the anti-snipe fee decreases. New Arc launches have no anti-snipe surcharge and pay the normal 1% fee from launch. Base, Robinhood, Monad, BSC and X Layer retain the 20-second schedule. Earlier pools keep their frozen settings.

The optional atomic Dev Buy is a one-time launch path on Base, Robinhood, Monad, Arc, BSC and X Layer. It pays the normal base swap fee but not the anti-snipe surcharge. Later buys use the ordinary trading rules.

Chain-specific token creation

Base mainnet

The protocol creates a native B20 token with a fixed supply and no administrator. One launch factory supports ETH, USDC, registered Coinbase crypto majors, and registered Base Stock Tokens. If the creator opts in, they may retain permission to update profile information only.

Robinhood, Monad, Arc, BSC and X Layer

o1 creates a standard ERC-20 with a fixed supply. It has no owner and no function to mint more tokens, pause transfers, upgrade the contract, or recover tokens. The selected route can pair it with a supported crypto asset or Stock Token.

Crypto and stock markets

Crypto

Crypto-paired launches use the selected chain’s native currency, including OKB on X Layer, the supported stablecoin for the selected chain, Monad WETH, or a registered Coinbase crypto major on Base. Swap fees and creator or referral claims use that same paired asset.

Stocks

Stock-paired contracts are deployed on Base, Robinhood and BSC; BSC supports crypto-paired and stock-paired creation. Buys spend the selected Stock Token, sells receive it, and all swap-fee claims for that pool are denominated in it. See Stock-paired launches.

Profile information, comments, and announcements

Feature	How it appears
Token profile	The image, description, website, X, Telegram, and other public fields are loaded from the IPFS metadata referenced by the token
Profile updates	When profile editing is enabled, the creator wallet can update the supported token identity and public information
Trade comments	A trader may attach a short comment of up to 32 UTF-8 bytes; it becomes public onchain data
Creator announcements	The current creator can publish updates through the separate announcement contract; original launch provenance remains unchanged

Comments and announcements are public onchain records. Announcements use a separate contract, so the creator does not gain permission to create tokens, control transfers, or remove liquidity.

What can change later

o1 governance can update supported paired assets, their opening-price references, creation fees, supply, liquidity settings, and swap fees for future launches. The announcement registry is bound once. Integrations must read the live fee before preparing a transaction.

Each completed launch keeps its token, original creator, paired asset, fee rates, opening price, liquidity range, and permanent position. Creator rights and the destination for future creator-fee credits can change through their explicit onchain processes. Later global configuration changes apply only to new launches.