> ## Documentation Index
> Fetch the complete documentation index at: https://docs.o1.exchange/llms.txt
> Use this file to discover all available pages before exploring further.
# How it works
> The complete o1 Launchpad lifecycle from setup and token creation to trading, fee claims, announcements, and vesting claims.
Creators use the o1 interface to configure a token and approve the launch transaction in their wallet. A stablecoin creation fee may require a token approval first. The launch contracts then create the token and its Uniswap market together. The blockchain is the source of truth, while o1 organizes confirmed public data so launches, trades, fees, and vesting are easy to view.
## End-to-end lifecycle
The creator supplies a name, symbol, image, quote currency, optional links and description, immediate allocations, vesting schedules, and a profile-editing preference.
The o1 confirmation screen presents the quote, fixed supply, creation fee, allocation and vesting totals, projected pool share, profile permission, and the predicted Base address when applicable.
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 quote, creation fee, supply, liquidity settings, and current chain time.
For an ETH launch, the wallet includes the creation fee in the launch transaction. A stablecoin launch may first ask for token approval. The creation fee goes directly to the platform fee receiver.
On Base, the protocol creates a native B20 token with no administrator. On Robinhood, o1 creates a fixed-supply ERC-20 with no owner or additional minting function. The fixed 1 billion supply is created once and divided between permanent pool liquidity, immediate recipient wallets, and any vesting schedules.
The launch contracts open the Uniswap v4 pool at the configured starting price. The part of the supply not allocated to recipients or vesting is placed into permanent liquidity.
After confirmation, the launch page shows the token profile, live market, trading interface, allocation disclosures, vesting status, trades, holders, and announcements.
## Where each asset lives
| Asset | Location | Who can move it |
| --------------------- | ------------------------------------------------------- | --------------------------------------------------------------- |
| Tradable token supply | The permanent Uniswap liquidity position | The launch contracts prevent its removal |
| Immediate allocations | Recipient wallets | Each recipient |
| Vested allocations | The vesting contract | Claims always go to the beneficiary chosen at launch |
| Creation fee | Platform fee receiver wallet | That wallet |
| 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
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.
The wallet submits a trade for the amount the user chose to spend or sell.
Uniswap calculates the result, and the launch contract applies the swap fee in the pool's quote currency.
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 during the first 16 seconds.
## Chain-specific token creation
The protocol creates a native B20 token with a fixed supply and no administrator. If the creator opts in, they may retain permission to update profile information only.
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.
## 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 creator recorded at launch can publish updates through the separate announcement contract |
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 quote currencies, opening prices, creation fees, supply, liquidity settings, swap fees, and the announcement contract for **future** launches.
Each completed launch keeps its token, creator, fee settings, opening price, liquidity range, and permanent position. Later configuration changes apply only to new launches.