Skip to main content
The o1 Launchpad interface combines wallet-signed actions, live contract reads, Uniswap v4 market data, public token profiles, and confirmed chain events. The blockchain remains authoritative for tokens, pools, balances, vesting, fees, and ownership.

​
Main pages

Trending now is a discovery view based on indexed market activity. Ranked views also require adequate pool coverage and current market data, and placement is dynamic. They are not recommendations or guarantees of future performance. Global search works across supported chains and accepts a token name, symbol, creator address, or token address. Results can be scoped to crypto-paired or stock-paired markets and filtered by paired asset. The currently published stock catalog is on Robinhood; another chain becomes available when its shared catalog and live factory are ready. Indexed historical data remains chain-scoped. A creator’s signed o1 profile, including its display name, bio, avatar, and socials, is separate from the optional onchain token profile permission chosen for each launch.

​
Discovery and transparency

The current interface adds context around the onchain market without replacing it as the source of truth:
  • homepage statistics distinguish activity in official launch pools from tracked activity across other pools for o1-launched tokens;
  • Trending now and ranked feeds use current market activity, liquidity, pool-coverage checks, and data freshness;
  • stock-paired rows show the selected Stock Token and its provider label;
  • token charts can mark launch start, creator or connected-wallet trades, announcements, and vesting unlocks;
  • allocation views separate immediate allocations from each beneficiary’s vesting schedule;
  • holder rows label known launch infrastructure, liquidity pools, exchanges, DeFi contracts, allocation recipients, the creator, and the connected wallet when data is available;
  • every token page carries a safety notice to review liquidity, live sell quotes, holders, allocations, and vesting before trading.
Discovery labels and third-party identity enrichment are informational. Contract addresses, balances, pools, and confirmed events remain authoritative.

​
Token creation flow

1

Configure and preview

The creator enters the token identity, socials, paired asset, optional distributions, vesting, and profile-editing preference. The page previews the fixed supply, opening value, free creation fee, and permanent pool.
2

Review the launch

The o1 confirmation screen shows the paired asset, supply, free creation fee, allocation and vesting totals, projected pool share, profile permission, and the predicted address when available.
3

Prepare and sign

After the creator confirms the review, the interface stores the public token profile on IPFS and refreshes the selected pair, route-specific factory, launch settings, and chain time. The creator then confirms the launch transaction in their wallet.
4

Open the token page

After confirmation, the token page presents the new token, live Uniswap market, allocation disclosures, vesting status, trades, holders, and public announcements.
The wallet is the only signing surface. o1’s interface and data services never hold the user’s private key.

​
Trading flow

The token page asks Uniswap v4 for a quote based on how much the trader wants to spend or sell. The interface applies the selected slippage limit and a 10-minute deadline, then asks the wallet to submit the swap through Uniswap’s Universal Router.
The wallet includes ETH in the swap transaction. No token approval is needed for the ETH input.
The same flow carries an optional referral and public trade comment. o1 always submits input-amount swaps, so its normal buy and sell flow remains available during the opening anti-snipe period.

​
Trade safeguards

​
Referral journey

  • A profile’s Referral action copies a global referral link.
  • A token page’s Referral link action copies a link for that token and chain.
  • A public Profile link is separate and does not set attribution by itself.
  • Token-specific attribution takes priority for that token. A previously saved global attribution is the fallback.
  • The interface may request one gasless signature to associate a browser-saved global referral with a connected wallet.
See Fees, anti-snipe, and referrals for the full precedence and validation rules.

​
Live and indexed information

The indexer keeps every registered historical and active contract suite queryable, while the create flow selects exactly one active factory for the chosen chain and route. This lets older launches remain visible without sending a new launch to a retired contract. Trade attribution uses the confirmed receipt and router context so smart-wallet activity is associated with the correct trader. The hook’s Trade.executor field alone is not treated as a user-wallet identity. After a transaction confirms, a page may briefly show that it is syncing while the indexed view updates. Live contract state and confirmed chain events remain the source of truth.