What o1bot is, and what it is not

o1bot owns three things: the X bot, the wallets it creates for users, and the web app. Everything on chain belongs to o1 Launchpad: the factory that creates the token, the Uniswap v4 pool, the hook that collects fees, the fee escrow, and the audits. o1bot does not run its own launch contracts and does not sit between you and o1.

That is why a token launched through o1bot is a normal o1 token. It shows up on o1, it trades on o1, and the creator fees go to the address o1 recorded at launch, which is your wallet.

Who pays for what

Your wallet pays o1's creation fee and the gas for the launch. If you add a dev buy, your wallet pays that too. o1bot never fronts fees or gas, never takes a cut of a launch, and never holds your keys.

o1bot earns from two places that never touch your launch: its own official token, launched through the same pipeline as everyone else's, and the 0.2% referral share o1 pays on trades that go through the o1bot app's swap.

How to read these docs

• Start gets you from zero to your first launch.
• Launching covers every option of the command and what each reply from the bot means.
• Money explains fees, your wallet, and the app.
• Developers documents how the bot builds a launch on chain, the contract addresses, and how to run the code.

What happens after you post

1. The bot reads the post and turns it into a launch command. If something required is missing, it asks one question.
2. It checks that your account is linked, the pair exists on o1's factory, and your wallet holds enough ETH.
3. It prepares the token metadata, mines an address ending in 01 as o1 requires, and simulates the whole launch.
4. It signs the launch from your wallet, waits for the receipt, and replies under your post with the token address, the o1 link, and the o1bot token page.

Trading opens immediately with o1's 20-second anti-snipe period. See Fees and economics.

Required values

Optional extras

Examples that work

The bot replies in the language you posted in.

What the bot will not guess

If the ticker, the name or the pair is missing, the bot asks one question instead of inventing a value. Amounts are taken literally: devbuy 0.05 means 0.05 ETH, and devbuy $50 is a question back to you because the bot does not convert currencies. Instructions aimed at the bot inside a post ("ignore your rules", "use the platform wallet") are ignored; the post is treated as data.

Stock-paired launches

A stock-paired token is created by the same factory with the same 0.001 ETH creation fee. The difference is the pool: it holds your token against the stock token, so buyers pay in the stock, and your creator fees arrive in the stock. That is the point for many creators: a coin that earns NVDA on every trade.

Because the pair asset is a stock token, a dev buy has to convert your ETH into that stock first. The bot finds a route through Robinhood's pools automatically; where none has liquidity, it tells you and offers a launch without the dev buy. Details in Dev buy.

Naming a pair

• Symbols always work: pair NVDA, pair usdg, pair $ETH.
• Aliases the bot understands: ether and ethereum for ETH, and company names that identify exactly one listed stock, such as nvidia, tesla, apple, google.
• If a name could mean two stocks, the bot asks which one.
• An asset that is not registered on o1's factory (DOGE, for example) gets a reply saying it is not available.

Tickers that collide with stocks

You cannot launch a token whose ticker equals a stock token symbol registered on the factory, so nobody mistakes your $TSLA for the tokenized stock. Pick another ticker; $TSLADOG is fine.

The list of registered pairs is refreshed from o1's published catalog. Every launch also re-reads the factory on chain, so a pair o1 removes cannot be selected even before the catalog is updated.

Why it exists

For 20 seconds after a pool opens, o1 charges a fee that starts at 99% and falls to the normal 1%. It stops bots from sniping the first blocks. The creator's own atomic buy is exempt: it pays the normal 1% and nothing more. Any buy in a later transaction, including one from you, pays the schedule like everyone else. The bot will never place a follow-up buy inside the window.

What you pay

The amount after devbuy is ETH, taken from your wallet on top of the creation fee and gas. devbuy 0.05 on a plain launch means the transaction carries 0.051 ETH plus gas.

Slippage protection

Before signing, the bot simulates the launch and reads how many tokens the buy would return. It then sets a minimum output 3% below that. If the chain moves against you between simulation and confirmation, the whole launch reverts and nothing is spent except gas. The bot tells you and you can post again.

How the ETH reaches the pool

• ETH pair: straight into the new pool. One hop.
• USDG pair: ETH is swapped to USDG on Robinhood's SwapX pool first, then into the new pool.
• Stock pair: either ETH to the stock directly, or ETH to USDG to the stock, depending on where the liquidity is. The bot tries every liquid route, simulates each, and uses the one that returns the most tokens.

Routes are discovered on chain at launch time. As of the September 2026 survey, 185 of the 194 stock tokens have a liquid route from ETH. For the rest, the bot replies that a dev buy is not available for that pair and offers to launch without it.

How it works

1. The bot resolves @alice to her stable X user id, so a later handle change does not break anything.
2. If she has never used o1bot, a wallet is created for her in advance, tied to that X id. When she signs in with X at o1bot.exchange, that wallet is already hers.
3. Your wallet launches the token as usual. You remain the on-chain creator and pay everything.
4. Right after the launch confirms, the bot sends a second transaction from your wallet that points the creator fee stream at her wallet. The bot replies only after both confirm, and mentions her so she knows.

Claiming as the recipient

Fees accumulate in o1's fee escrow until claimed. The recipient signs in at o1bot.exchange, opens their wallet, and claims. A brand-new wallet has no ETH for gas, so o1bot covers the first claim's gas; after that the recipient's wallet pays its own way.

Who can receive fees

• Any real X account except suspended ones.
• Not the bot's own accounts and not o1's accounts.
• You keep the other creator rights (metadata, transferring creator rights) unless you transfer them separately on o1.

Image rules

What gets recorded

The token's contract metadata is a small JSON document with the name, symbol, image, a link to the o1bot token page, and attribution to the post that launched it: the author's handle, X user id, and the post id. Anyone can verify which post created which token.

Metadata is fixed at launch. The o1bot creates every token with editing disabled, which is also what o1 marks as the immutable default.

Launched

o1bot.exchange @o1bot_exchange

Launched $RUGRAT — Rugrat, paired with ETH on Robinhood Chain. Token 0x4dB2…Bf01 o1: o1.exchange/token/… · o1bot: o1bot.exchange/t/… Dev buy: 0.05 ETH. Fees go to @alice.

The launch confirmed. The dev buy and fees-to lines appear only when used. The full token address is in the o1bot token page.

One question

o1bot.exchange @o1bot_exchange

Which pair should $ABC trade against? ETH, USDG or a stock token like NVDA.

A required value was missing or ambiguous. Reply to the bot, or post a new complete command.

Not linked yet

o1bot.exchange @o1bot_exchange

Link this X account first at o1bot.exchange, then post again.

The posting account has never signed in at o1bot.exchange, or has not allowed the bot to sign from its wallet.

Balance is short

o1bot.exchange @o1bot_exchange

Your wallet is 0.0013 ETH short for this launch. Send ETH on Robinhood Chain to 0x4E2a…9C01, then post again.

Exact shortfall including gas. Top up and repost; nothing was spent.

Other outcomes

Rate limits (o1bot)

Token fields (o1 limits, o1bot rules)

What the bot never does

• Never guesses a ticker, name, pair, chain or amount you did not write.
• Never signs anything but a launch, the ERC-20 approval a launch may need, the fee-recipient update, or a fee claim, and only to o1's contracts.
• Never buys after the launch transaction, and never inside the anti-snipe window.
• Never pays from a o1bot wallet on your behalf, and never sets o1bot as the creator of your token.

Creation fee

0.001 ETH per launch, paid to o1 by your wallet, for every pair including stock pairs. Plus network gas, roughly 2.2 million gas for a plain launch and 2.7 million with a dev buy. The fee is a setting o1 can change; the bot reads the live value before every launch and tells you the exact amount if your wallet is short.

Swap fee

Every trade in the pool pays 1% of the paired asset, split three ways:

Fees are always in the pair asset: an ETH pool pays ETH, a USDG pool pays USDG, an NVDA pool pays NVDA. When a trade has no valid referrer, o1 keeps the 0.2%.

The opening 20 seconds

Trading is open from the first block, but the total fee starts at 99% and falls linearly to 1% over 20 seconds. Everything above 1% goes to o1. The creator's atomic dev buy is exempt; every later buy is not.

What o1bot earns

• The referrer share (0.2% of trades) on swaps made through the o1bot app. o1 pays it; traders pay nothing extra. o1 rejects a referrer that equals the creator or the fee recipient, so o1bot's referrer wallet is a separate address from any user wallet.
• Creator fees on o1bot's own token, launched through the same pipeline as everyone else's.

There is no fee on launches, no fee on claims, nothing taken from user wallets.

The wallet

Signing in with X at o1bot.exchange creates an embedded wallet through Privy, tied to your X account. It is a normal Ethereum address. You can see it, top it up, export its private key, and use it anywhere. o1bot never sees the key.

The permission you grant

For the bot to launch from your wallet, you allow "delegated signing" once in the app. Until you do, the bot replies that your account is not linked. You can revoke it in the app at any time.

What the bot is allowed to sign

The signer inside the bot refuses everything that is not on this list, before the request ever reaches Privy:

No plain transfers, no other contracts, no message signing, no signing on other chains. A post cannot turn into arbitrary calldata; the bot only fills the fields of those four calls. Every signed transaction is logged with the post id, your X id, your wallet, and a hash of the calldata.

Things worth knowing

• You are the on-chain creator. o1 records your wallet as the original creator; that cannot be changed by o1bot.
• Keep only what you plan to spend in the launch wallet. It is a hot wallet by design.
• The fees to recipient's wallet is created in advance and handed to them on their first sign-in. Until then nobody can spend from it.
• o1bot's treasury and referrer wallets are separate addresses that never sign user launches.

Available now

• Sign in with X and create your wallet.
• See your address, your ETH balance on Robinhood Chain, and whether the bot is allowed to sign.
• Export your private key.

Coming soon

• Board and token pages are live in the app: every token launched through o1bot, with the post that launched it, chart, trades, holders and price.
• Swap: buy and sell through o1's pool from your o1bot wallet, with the anti-snipe countdown shown live. Trades made here carry o1bot as the referrer.
• Claim fees: collect your creator fees from o1's escrow, grouped by asset.

Stages

Stack

TypeScript throughout. viem for chain reads and writes, Privy for wallets and login, the Anthropic SDK for the parser, Postgres with Prisma for users, mentions, launches and the signed-transaction audit log, Redis for the queue and dedupe, Next.js for the app. Verified contract ABIs are vendored from two independent sources and must agree.

Errors the executor understands

Dev-buy route data

The launch-buy adapter is not source-verified on any explorer, so its route format was reverse-engineered from live transactions and is pinned byte for byte in tests. A route is abi.encode(Step[]) where a step is (kind, tokenIn, tokenOut, pool, fee, tickSpacing, hooks, hookData); kind 1 is a SwapX V3 pool, kind 2 a Uniswap V4 pool. The last step is always the new launch pool with fee 0 and o1's hook.

Active launch suite (launchpad-v4-minimal)

Configuration version 14 at the snapshot; creation enabled; native launch fee 0.001 ETH; tick spacing 200; supply 1,000,000,000 tokens.

Uniswap and pairs

The 194 stock token addresses are in o1's robinhood-stock-quotes.json, mirrored in the repo's config/.

Historical factories

o1 has rotated its Robinhood suite four times before the active one. Tokens created by those factories are still o1 tokens; the indexer keeps every suite from its first block and resolves a token by chain id and originating factory, never by assuming the current one.

Explorer: robinhoodchain.blockscout.com. Sources: o1 production contracts, launch-contract-suites.json.

Layout

copyconfig/            o1 contract snapshot, regenerated with pnpm o1:sync
abis/              verified ABIs (Sourcify + Blockscout must agree)
packages/shared    env, chain + RPC fallbacks, o1 registry, tx allow-list
packages/db        Prisma schema: users, mentions, launches, signed-tx audit
packages/wallet    Privy: X user to wallet, pregeneration, guarded signer
packages/executor  factory reads, salt mining, metadata, routes, planLaunch
packages/parser    Claude mention parser with fixtures
apps/web           Next.js app (Privy X login, wallet, onboarding)
apps/bot           the worker

Setup

copypnpm install
cp .env.example .env        # Privy, X, Anthropic, Pinata keys; keep DRY_RUN=true
pnpm o1:sync                # refresh config/o1.json from docs.o1.exchange
pnpm abi:vendor             # re-vendor ABIs when o1:sync reports drift
pnpm db:generate && pnpm db:push
pnpm typecheck && pnpm test

Dry-run a launch

Simulates the whole thing against the live factory and sends nothing. A random creator is funded virtually inside the simulation, so it works with an empty wallet.

copypnpm simulate --name "Rugrat" --symbol RUGRAT --pair ETH
pnpm simulate --name "Rugrat" --symbol RUGRAT --pair ETH --devbuy 0.01
pnpm simulate --name "Nvidia Dog" --symbol NVDOG --pair NVDA --devbuy 0.01

Test the parser

copypnpm parse '@o1bot_exchange launch $RUGRAT "Rugrat" pair ETH on robinhood'
pnpm parse --fixtures       # 24 fixtures against the live model

Environment

Is it free?

o1bot charges nothing. You pay o1's 0.001 ETH creation fee and gas from your own wallet, like any launch on o1.

Is the token different from one launched on o1's site?

No. Same factory, same pool, same fees, same audits. The only extra is the metadata line that records which post launched it.

Can I use my own wallet instead of the one o1bot creates?

Not for bot launches. The bot needs a wallet it is allowed to sign from, and that is the Privy wallet tied to your X account. You can export its key and use it anywhere afterwards.

I posted and nothing happened.

Check three things: the post mentions @o1bot_exchange and is not a quote or retweet of the bot; your account is linked and the bot is allowed to sign; the wallet holds enough ETH. If the bot replied with a question, answer it in a new post with the full command.

Can I change the name or image after launch?

No. Tokens launched through o1bot are created with metadata editing disabled.

Stock pair: what do I actually earn?

0.5% of every trade, paid in the stock token. Claim it from the app when it is live, or on o1 directly with your wallet.

The dev buy failed but the token exists?

That cannot happen. A dev buy is atomic with the launch: if the buy fails, the whole launch reverts and no token is created.

When is Base coming?

Not in v1. The bot, the pairs and the docs are Robinhood Chain only for now.

Changelog

2026-09-07

• Board and token pages with chart, trades, holders and the genesis post; indexer for swaps and prices. Only tokens launched through the bot are listed.
• Privacy policy, terms of use and how-it-works pages; repository published under the MIT license.
• Scope set to Robinhood Chain only for v1.
• Verified ABIs vendored from Sourcify and Blockscout; token address prediction validated against four live launches.
• Dev buy for ETH, USDG and 185 stock pairs through on-chain route discovery.
• Mention parser with structured output and deterministic normalisation.

2026-09-06

• Repository scaffolded: wallet, database schema, o1 snapshot, transaction allow-list, onboarding page.