bitpro가 원문에서 글자만 모은 내용이에요. 표·그림·수식은 빠지거나 깨질 수 있어요. 전체 35쪽 중 11쪽
Owner wallet to sign each launch.
## What the Bot can do
The permission is restricted to reviewed launch-factory operations: create a supported token, or create and execute the explicitly requested atomic Dev Buy. Launch requests are also checked for the connected X identity, supported chain and quote, valid fields and funding.
It does not grant general wallet access.
| Operation | Restricted Bot permission |
| - | - |
| Supported token launch | Allowed while permission is valid |
| Supported launch with explicit Dev Buy | Allowed while permission is valid and funds are available |
| Ordinary token swap or transfer | Not allowed |
| Withdraw funds | Not allowed; requires Owner wallet |
| Claim fees or edit token metadata | Not allowed by this launch permission |
| Renew, revoke or change permissions | Not allowed; requires Owner wallet |
## Duration and spending
New setup and Owner-approved renewals use a **30-day** launch permission. The portal shows your account's actual expiry.
<Warning>
The current permission version has **no cumulative native-asset spending cap**. Its restriction is which launch operations it can call, not a lifetime ETH budget. ETH already held by the account, and ETH deposited later, can fund permitted launches while access remains valid. Fund only the balance you intend to make available for this purpose.
</Warning>
Older permissions can retain a **0.10 ETH cumulative native-value cap** until replaced through Owner-approved renewal. Depositing more ETH does not raise that cap. Check the permission installed on your account instead of assuming every account has the newest version.
Application request limits and per-Post Dev Buy amounts do not turn an uncapped permission into a cryptographic cumulative spending limit.
## Renew or revoke
Use **Permissions** in the o1 Bot portal to inspect access, renew it or revoke it. These actions require your Owner wallet's approval. Wait for onchain confirmation before relying on the changed permission state.
Revocation prevents subsequent use of that permission; it does not reverse a transaction that already executed. Check any pending or uncertain launch before taking further action.
## X identity and session safety
* Protect the connected X account: a valid launch instruction from that identity can spend smart-account funds within the permitted operations.
* Disconnecting or switching your connected Web3 wallet also signs you out of the current X website session and clears the previous account display. See [switching wallets or X accounts](/launchpad/bot/wallet-and-fees#switch-wallets-or-x-accounts).
* Website sign-out does not unlink the X identity, change the smart account's Owner or revoke an onchain permission. It does not by itself stop authorized Bot launches.
* Sending [stop](/launchpad/bot/commands#stop-future-requests) opts the X identity out of future requests; it does not revoke the onchain permission.
* Deleting or editing a Post is not a reliable way to cancel a transaction already being processed.
* Never include a seed phrase or private key in a Post, a metadata field or a support message.
For a failed setup, expired permission or uncertain transaction, see [Troubleshooting](/launchpad/bot/troubleshooting).
# Launch from X
Source: https://docs.o1.exchange/launchpad/bot/quickstart
Connect your X account, prepare a Base smart account, and launch a token with o1 Bot V1.
Mention **@o1\_bot** in an X Post to create a token and open its market. For the standard setup flow, your Base smart account is the creator and pays for the launch. Your connected Owner wallet controls that account.
<Note>
Bot V1 supports **Standard crypto-paired launches on Base only**. The wider chain, Stock Token and Tax options in the web create form are not Bot commands.
</Note>
## Your first launch
<Steps>
<Step title="Connect X and your Owner wallet">
Open the [o1 Bot portal](https://launch.o1.exchange/o1-bot), select Base using the global chain selector, and connect the X account you will post from. Connect the Web3 wallet that will own your smart account.
</Step>
<Step title="Activate your Base smart account">
Review the restricted launch permission and approve setup with your Owner wallet. Wait until activation and the permission have been verified onchain.
Setup does not launch a token. Read [Permissions and safety](/launchpad/bot/permissions) before approving access.
</Step>
<Step title="Fund the smart account">
Use **Deposit** in the portal. Keep enough ETH in the smart account for the launch fee, network gas, and any optional Dev Buy. Your Owner wallet needs its own ETH for the deposit transaction's gas.
See [Wallet and fees](/launchpad/bot/wallet-and-fees) for who pays each cost.
</Step>
<Step title="Post your launch request">
Copy the example below, replace the name and symbol, and **attach exactly one PNG, JPG or WEBP image**. Send it from your connected X account.
```text theme={null}
@o1_bot Launch on Base
Name: My Token
Symbol: MYTOKEN
Quote: ETH
Description: A community token.
```
A valid request can execute without a second wallet confirmation. Review all fields before posting. Images and token details become public.
</Step>
<Step title="Check the result">
The Bot replies with the launch result or a correction request. After success, open the token link and inspect the transaction and token contract address. The portal also shows recent launch activity.
If submission is pending or its outcome is unknown, do not send a duplicate request. Follow [Troubleshooting](/launchpad/bot/troubleshooting).
</Step>
</Steps>
## What happens to the tokens?
A launch creates the fixed supply and places it into permanently locked pool liquidity. Being the creator does **not** automatically put that supply in your wallet. To buy tokens during creation, explicitly include an [optional Dev Buy](/launchpad/bot/dev-buy); bought tokens go to your smart account.
## Posting in an existing conversation
You can start another launch in the same conversation. Include a complete new launch instruction, all required fields and a new attached image. A fresh launch does not inherit the previous request's image, chain or Dev Buy.
To correct a request that is waiting for details, reply directly to that request or the Bot's correction prompt. See [Replies and corrections](/launchpad/bot/commands#replies-and-corrections).
<Accordion title="Invited creators launching without setup">
Some approved creators can use a platform-funded launch path before setting up a smart account. This requires explicit eligibility; mentioning the Bot does not grant access.
This path does not support Dev Buy. If you already have a smart account, an insufficient balance or invalid permission does not automatically switch your launch to platform funding.
To request Creator Rights for an eligible pre-setup launch, complete setup and use the portal's claim flow. There is no application fee, but review and the onchain transfer process are still required. Creator Rights do not grant minting or transfer controls, and previously credited fees do not move to the new recipient.
</Accordion>
<CardGroup>
<Card title="X commands" icon="terminal" href="/launchpad/bot/commands">
Required fields, optional metadata, help, and stopping future requests.
</Card>
<Card title="Add a Dev Buy" icon="coins" href="/launchpad/bot/dev-buy">
Buy tokens atomically with an ETH-paired launch.
</Card>
</CardGroup>
# Troubleshooting
Source: https://docs.o1.exchange/launchpad/bot/troubleshooting
Resolve launch input, funding and permission problems without creating duplicate transactions.
Start with the Bot's reply and the portal's request activity. A generic error message alone does not identify its cause.
## Common problems
| What you see | What to check |
| - | - |
| No reply yet | Confirm the Post mentions @o1\_bot, was sent from the intended X account, and is a direct Post or reply. Check portal activity before posting again |
| No reply after help, template and a partial field | These can consume one request's three-Post classification limit. See [Help and template follow-ups](#help-and-template-follow-ups) |
| Buy, sell or withdraw only returns instructions | Expected: these are guidance replies, not executable X trading or withdrawal commands |
| No token link in a buy or sell reply | Reply directly to your own confirmed launch's success message. The Bot will not guess a token from ambiguous context |
| Specify an enabled chain | Include `Launch on Base` or `Chain: Base` in the request. The portal's selected chain is not enough |
| Missing or invalid image | Attach exactly one PNG, JPG or WEBP photo within the [image limits](/launchpad/bot/commands#fields) |
| Missing name, symbol or other details | Reply directly to the correction prompt from the same X account with the requested field |
| Setup required | Connect X and the Owner wallet, then finish Base smart-account activation |
| X signed out after disconnecting or switching wallets | Expected: the website session follows wallet changes. Connect the intended wallet and X account again; existing smart accounts require their bound Owner. See [account switching](/launchpad/bot/wallet-and-fees#switch-wallets-or-x-accounts) |
| Insufficient funds | Fund the **smart account**, not just the Owner wallet, for the launch fee, gas and any Dev Buy |
| Permission invalid or expired | Inspect Permissions in the portal. The Owner may need to renew access and confirm it onchain |
| Dev Buy unsupported | Use the setup smart-account path on Base with `Quote: ETH` and an explicit positive ETH amount |
| Request limit reached | Wait for capacity to become available. Recorded failed requests can count toward the smart-account limit |
| Could not prepare this launch | Check the recorded request detail. Preparation can fail for different reasons, including provider or permission-check errors; it is not necessarily a balance problem |
## When is it appropriate to retry?
<Tabs>
<Tab title="Awaiting correction">
Reply directly to the current launch correction prompt. Do not start another complete launch merely to supply a missing field. A request allows up to two guidance or correction replies in total; help and template follow-ups can consume those replies too.
</Tab>
<Tab title="Nothing submitted">
Fix the stated cause first. If the request is closed and the Bot explicitly confirms nothing was submitted, send a complete new launch request with its own image. It may be in the same conversation.
</Tab>
<Tab title="Pending or unknown">
Do not repost or assume failure. Inspect the request and any transaction link, and wait for its outcome to be resolved. An unknown submission might already have reached the chain.
</Tab>
</Tabs>
<Warning>
A new Post is a new request and can create another token. Reusing a name or symbol is not a deduplication mechanism.
</Warning>
## Help and template follow-ups
A template is an example, not a saved launch draft. After requesting it, send a complete launch instruction with your own fields and one supported image. Replying only `Symbol: FIX` does not adopt the other sample values.
V1 currently counts help and template messages toward the same three-Post classification limit when they continue one request. After two guidance or correction replies, a third incomplete message can close the request without a final explanation. This is a known limitation, not evidence of an X delivery failure.
If you only asked for help and supplied a partial field, use a complete launch request when ready. If you also sent a complete launch or saw a pending submission, check its status before reposting. Do not infer a failed transaction from silence.
Standalone buy, sell and withdraw guidance uses a separate path and does not use up the active launch's correction attempts. It still respects reply limits and opt-out. See [guidance behavior](/launchpad/bot/commands#buy-sell-and-withdraw-guidance).
## Launch succeeded, but I do not see tokens
Creating a token does not allocate the initial supply to your wallet. Without a Dev Buy, the supply goes into locked liquidity.
If you requested a Dev Buy, check the confirmed transaction and the **smart account's** token balance, not only the Owner wallet. Use the contract address to identify the token. A delayed asset list or missing reply is not proof that the purchase failed.
See [Verify the purchase](/launchpad/bot/dev-buy#verify-the-purchase) before retrying.
## Activation or deposit failed
Check the selected network, connected Owner wallet, wallet rejection messages and available Base ETH for gas. An HTTP or RPC error does not by itself mean an X permission or API-key permission is missing.
If a transaction was sent, inspect its receipt before repeating setup or a transfer. A successfully activated smart account does not need to be recreated just because a later request fails.
## What to include in a support report
Share the Post URL, approximate time, Base smart-account address, displayed error, request status and transaction hash if available. Explain whether the request included Dev Buy and its amount.
Do not share private keys, seed phrases, API secrets, authentication headers or private RPC URLs. Use the official [community channels](/community/socials) for help.
# Wallet and fees
Source: https://docs.o1.exchange/launchpad/bot/wallet-and-fees
Understand smart-account balances, deposits, withdrawals, Max, and who pays gas.
Your **Owner wallet** is the connected Web3 wallet that controls your **Base smart account**. They are separate addresses with separate balances. Sending ETH to the Owner wallet does not fund the smart account automatically.
## Switch wallets or X accounts
Disconnecting your connected Web3 wallet or switching to a different wallet address also signs you out of the current X website session. The portal clears the previous X account and its displayed account data. This also applies when you change accounts in your wallet extension or disconnect on another page of the site.
To use a different wallet and a different X account, disconnect the current wallet, connect the other wallet, then use **Connect X** to authorize the other X account. For an existing smart account, use its bound Owner wallet. For a new account, complete setup with the intended wallet and X identity.
* First-time setup still allows you to connect X before connecting your first wallet.
* Changing only the network while keeping the same wallet address does not sign you out of X.
* If sign-out fails, the portal keeps the old account hidden. Selecting **Connect X** retries the sign-out before starting another login.
<Warning>
Signing out does not unlink an X identity from its smart account, change the Owner, delete assets or revoke the Bot's onchain permission. Previously authorized Bot launches can continue while permission and other execution requirements remain valid. To remove that permission, use [Permissions](/launchpad/bot/permissions#renew-or-revoke) and confirm revocation with the bound Owner wallet.
</Warning>
## Who pays?
| Action | Funds and gas |
| - | - |
| Activate or manage permissions | Owner wallet signs and pays the required transaction gas; setup can also fund the smart account's activation needs |
| Deposit through the portal | Owner wallet sends ETH and pays the deposit gas |
| Launch from X | Smart account pays the launch fee and execution gas |
| Launch with Dev Buy | Smart account also pays the explicit purchase amount |
| Withdraw through the portal | Assets leave the smart account; Owner wallet signs and pays gas from its own ETH balance |
This table describes the user-owned smart-account path. Approved no-setup creators use a separate platform-funded launch path without Dev Buy.
## Deposit ETH
Choose **Deposit** in the [o1 Bot portal](https://launch.o1.exchange/o1-bot), review the Base smart-account destination, and confirm in your Owner wallet.
* **Max** is the maximum transferable amount after reserving the estimated deposit gas in your Owner wallet. It is not an account deposit limit or a Bot permission limit.
* A deposit only moves funds. It does not launch a token, request a Dev Buy or extend permission expiry.
* Use ETH on **Base**. Do not treat a balance on another chain as available for this account's Base launch.
## Budget for a launch
```text theme={null}
Required smart-account ETH
= current launch fee + optional Dev Buy amount + execution gas
```
The portal shows the current launch fee; gas varies with execution and network conditions. Do not treat an old screenshot or example purchase amount as an all-in quote. See [Live configuration](/launchpad/reference/live-configuration) for dated protocol fee snapshots.
A small balance can remain after setup if not all activation funding was used. To identify the origin of a specific balance, check that account's incoming transfers and transaction history in the explorer.
<Note>
Account balance and permission limits are separate. Depositing ETH does not grant new permission, and an active permission does not supply funds. Review the [permission version and expiry](/launchpad/bot/permissions) before funding.
</Note>
## Your assets
The Wallet view lists assets actually held by the smart account, including tokens received through Dev Buy. Tokens you created are not automatically wallet holdings, and creator status does not mean you own the entire supply.
Use the contract address and explorer link to distinguish assets with the same name or symbol. The portal can lag behind a confirmed transaction while balances and activity refresh.
## Withdraw to your Owner wallet
Choose **Withdraw** next to an asset, or open the general Withdraw action and select an asset. Review the amount and recipient before confirming.
* V1 sends withdrawals to the **bound Owner Web3 wallet on Base**, not an arbitrary pasted address.
* ETH and supported token holdings can be withdrawn.
* Your Owner wallet signs and needs enough Base ETH to pay gas, including when withdrawing a token.
* For ETH, Max can withdraw the smart account's full available balance because the Owner wallet pays this withdrawal's gas. Doing so can leave the smart account unable to launch again until funded.
* The Bot's restricted launch permission does not authorize it to withdraw assets.
If a withdrawal's confirmation is uncertain, check the existing transaction first. Do not send another withdrawal until you know the previous result.
## Trade tokens after launch
The Bot cannot buy or sell existing tokens through X. To sell tokens held in the smart account, first withdraw them to the bound Owner wallet, then connect that wallet on the token's trading page and review the trade yourself.
Replying `@o1_bot sell it` or `@o1_bot buy more` directly to your launch confirmation can return the verified token page. `@o1_bot withdraw` points to the portal. These are [guidance replies](/launchpad/bot/commands#buy-sell-and-withdraw-guidance), not executed transactions; you still review and sign wallet actions manually.
# Stock-paired launches
Source: https://docs.o1.exchange/launchpad/create/stock-paired-launches
Launch a Base, Robinhood, BSC or X Layer token against a supported Stock Token with permanent Uniswap v4 liquidity and stock-denominated trading fees.
Stock-paired launches let a creator open a market between a new o1 launch token and a supported Stock Token on Base, Robinhood, BSC or X Layer. The Stock Token is the pool's paired asset, so it sets the opening-price reference, is used to buy the launch token, and is received when the launch token is sold.
<CardGroup>
<Card title="Choose your stock pair" icon="chart-line">
Choose from the supported Stock Tokens on Base, Robinhood, BSC or X Layer.
</Card>
<Card title="Current creation fee" icon="rocket">
Stock-paired launches use the same creation fee as crypt프로젝트로 돌아가기
