Skip to main content
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 selected launch product’s 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 chooses Standard, Tax or $O launches, then supplies a name, symbol, image, paired asset, optional links and a profile-editing preference. Tax launches also configure their taxes, allocations, dividend threshold and anti-sniping choice. $O launches use the displayed Factory burn rates without fee-allocation controls.
2

Review the launch

The o1 confirmation screen presents the paired asset, fixed supply, permanent liquidity, current creation fee, profile permission, and the token address preview.
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 any displayed creation fee plus the chain’s network gas. Base and Robinhood Standard/Tax use a 0.001 ETH fee. $O launches on Base and Robinhood have no creation fee. 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

Base Standard creates a native B20 token with no administrator; Base Tax and $O create fixed-supply ERC-20s. 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

​
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 short, route-specific 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 Hook applies the launch’s fees. Standard fees and Tax protocol/creator/dividend/integrator credits use the paired asset. A Tax burn allocation uses launched tokens. The $O launch Hook instead burns wstO quote fees immediately.
4

Settle the swap

The user receives the trade output. Ordinary recipient fees become claimable independently. Tax dividends are assigned to eligible holders during the trade; collected burn tokens can be sent to the dead address separately.
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 Standard launches have no anti-snipe surcharge and pay the normal 1% fee from launch. The documented Standard settings on Base, Robinhood, Monad, BSC and X Layer use a 20-second schedule. Tax on Base, Robinhood, BSC, Monad, X Layer and Arc has creator opt-in and declines toward its own buy or sell total. 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 ordinary fee for the selected product, including the Tax buy total, but not the anti-snipe surcharge. Later buys use the ordinary trading rules. $O launches have no anti-sniping surcharge or fee exemption. Their ETH Dev Buy acquires $O, deposits it for wstO and pays the normal launch-pool buy burn. Later trades can settle in ETH, USDC, $O or wstO when the whole route is executable. See the complete flow.

​
Chain-specific token creation

Standard creates a native B20 token; Tax and $O create fixed-supply ERC-20s. Standard and Tax each have a factory for supported crypto assets and Stock Tokens; the separate $O factory launches against wstO. If the creator opts in, they may retain permission to update profile information only.

​
Crypto and stock markets

Crypto-paired launches use the selected chain’s native currency, a supported stablecoin or another registered crypto asset. Standard fees and Tax creator/protocol/integrator/dividend rewards use that asset; Tax burn credits use launched tokens.

​
Profile information, comments, and announcements

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 economic-policy changes apply only to new launches. Tax Dividend exclusions, receivers and asset recovery have separate administrative controls.