Skip to main content
Creators use the o1 interface to configure a token and approve the launch transaction in their wallet. Token creation is currently free, apart from network gas. The launch contracts 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, 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, free 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 free launch

The creator approves the launch transaction and pays only the chain’s network gas. The current creation fee is zero on every available production route.
5

Create the token

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.
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

Open the launch page

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

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 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 during the first 16 seconds.

​
Chain-specific token creation

The protocol creates a native B20 token with a fixed supply and no administrator. Current creation pairs it with ETH, USDC, or a registered Base Stock Token. If the creator opts in, they may retain permission to update profile information only.

​
Crypto and stock markets

Crypto-paired launches use ETH or the supported stablecoin for the selected chain. Swap fees and creator or referral claims use that same paired asset.

​
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, stock opening-price references, creation fees, supply, liquidity settings, swap fees, and the announcement contract for future launches. The current creation fee is zero. Each completed launch keeps its token, creator, fee settings, opening price, liquidity range, and permanent position. Later configuration changes apply only to new launches.