bitpro가 원문에서 글자만 모은 내용이에요. 표·그림·수식은 빠지거나 깨질 수 있어요. 전체 35쪽 중 15쪽
including the image, description, website, X, and Telegram;
* extra profile information.
This permission cannot create more tokens, change balances, pause transfers, upgrade the token, or remove liquidity.
## Creator rights
The active launch factory records the launch-time `originalCreator` permanently and separately tracks the `currentCreator`. Standard and Tax additionally track a `creatorFeeRecipient`, which can be changed for future creator-fee credits. The current creator can propose a two-step creator-rights transfer. Announcement authority follows the current creator. Metadata editing also follows that creator when profile editing was enabled at launch. \$O launches retain these project rights without a creator-fee recipient or fee claims.
Creator rights are not token ownership. They do not grant minting, transfer control, upgrades, balance recovery, or liquidity removal. Already credited fee balances stay with the recipient that earned them. The current application does not expose creator-rights management controls; direct integrations must use the verified active-factory ABI.
## Transaction safety
The factory rejects a launch if:
* the quote is no longer registered;
* the unique launch identifier was already used;
* the launch settings changed after the app prepared the transaction;
* the deadline has passed;
* the current creation fee or transaction value does not match the active factory configuration;
* profile or liquidity requirements fail;
* the token cannot be created exactly as shown;
* opening the pool would require the creator to supply the paired asset.
The frontend refreshes the launch settings and chain time immediately before submission. If a protected global setting changes while the transaction is pending, the call stops instead of silently using a different configuration. A paired asset's opening-price refresh intentionally uses the latest registered frame when the launch executes.
## Creation result
After confirmation, the app shows the token address and live pool. It also records the paired asset, creation fee, creation route, and market settings from the confirmed transaction. Developers can find exact function and event names in [Functions and events](/launchpad/reference/events-functions).
BSC supports crypto-paired and stock-paired creation. Its 0.003 BNB launch fee is separate from gas and any Dev Buy input. See [BSC Standard configuration](/launchpad/reference/live-configuration#bsc-mainnet) and [BSC Tax configuration](/launchpad/reference/live-configuration#bsc-tax-suite).
X Layer uses the same immutable ERC-20 creation flow and a 0.02 OKB launch fee. Quotes include native OKB (18 decimals), USDC (6 decimals), xETH (18 decimals) and 45 wrapped stocks (18 decimals). WOKB is a separate routing wrapper. Ordinary creation needs only the OKB launch fee and gas, with no paired-asset deposit. Optional atomic Dev Buy adds the entered OKB amount to the launch fee. See [X Layer configuration](/launchpad/reference/live-configuration#x-layer-mainnet).
# How it works
Source: https://docs.o1.exchange/launchpad/how-it-works
The complete o1 Launchpad lifecycle from setup and token creation to trading, fee claims, announcements, and staking.
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
<Steps>
<Step title="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.
</Step>
<Step title="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.
</Step>
<Step title="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.
</Step>
<Step title="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.
</Step>
<Step title="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.
</Step>
<Step title="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.
</Step>
<Step title="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.
</Step>
<Step title="Open the launch page">
After confirmation, the launch page shows the token profile, live market, trading interface, trades, holders, and announcements.
</Step>
<Step title="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.
</Step>
</Steps>
## Where each asset lives
| Asset | Location | Who can move it |
| - | - | - |
| Initial token supply | Seeded into the permanent Uniswap liquidity position | Trading moves tokens between the pool and wallets; the launch position itself cannot be removed |
| Staked wallet tokens | The separate staking contract | The participant can withdraw principal according to the selected vault's fixed policy |
| Creation fee | Paid to the configured fee recipient in the launch transaction | The creator's wallet pays the exact live fee shown before signing |
| Accrued swap fees | A dedicated claimable balance for each recipient | Standard creator/platform/referrer, or Tax creator/protocol/integrator, according to the launch configuration |
| Tax dividends | Rewards earned as trades happen | Eligible holders claim their earned share |
| Tax collected burn tokens | Held until someone burns them | Anyone may send them to the dead address; no payment to the caller |
| \$O launch wstO fee | Collected and burned by the Hook during each successful swap | Actual wstO supply reduction, with no claim or later burn action |
| \$O backing wstO | The separate wstO vault | Vault redemptions return underlying; fee-only burns leave it there |
| User trade funds | The user's wallet and the Uniswap pool during the trade | The transaction approved by the user |
## Swap lifecycle
<Steps>
<Step title="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.
</Step>
<Step title="Sign with the wallet">
The wallet submits a trade for the amount the user chose to spend or sell.
</Step>
<Step title="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.
</Step>
<Step title="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.
</Step>
</Steps>
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](/launchpad/wsto/overview#create-and-buy).
## Chain-specific token creation
<Tabs>
<Tab title="Base mainnet">
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.
</Tab>
<Tab title="Robinhood, Monad, Arc, BSC and X Layer">
o1 creates a standard ERC-20 with a fixed supply. It has no owner and no function to mint more tokens, pause transfers, upgrade the contract, or recover tokens. The selected route can pair it with a supported crypto asset or Stock Token.
</Tab>
</Tabs>
## Crypto and stock markets
<Tabs>
<Tab title="Crypto">
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.
</Tab>
<Tab title="Stocks">
Stock-paired launches are supported on Base, Robinhood, BSC and X Layer. Buys spend the selected Stock Token, sells receive it, and recipient fees and Tax dividends are denominated in it. Tax burn credits remain in launched tokens. See [Stock-paired launches](/launchpad/create/stock-paired-launches).
</Tab>
</Tabs>
## Profile information, comments, and announcements
| Feature | How it appears |
| - | - |
| Token profile | The image, description, website, X, Telegram, and other public fields are loaded from the IPFS metadata referenced by the token |
| Profile updates | When profile editing is enabled, the creator wallet can update the supported token identity and public information |
| Trade comments | A trader may attach a short comment of up to 32 UTF-8 bytes; it becomes public onchain data |
| Creator announcements | The current creator can publish updates through the separate announcement contract; original launch provenance remains unchanged |
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](/launchpad/tax/dividends#exclusions-and-administration).
# Data and AI access
Source: https://docs.o1.exchange/launchpad/integration/data-ai
Public documentation, machine-readable launchpad configuration, onchain data, and safe wallet-based agent workflows.
o1 Launchpad documentation and production configuration are available in formats that work for people, search tools, coding agents, and other AI clients.
## Documentation resources
| Resource | Access | Use |
| - | - | - |
| Documentation index | [Open `llms.txt`](https://docs.o1.exchange/llms.txt) | Discover available documentation pages |
| Full documentation | [Open full text](https://docs.o1.exchange/llms-full.txt) | Retrieve the public documentation as one text corpus |
| Page Markdown | Add `.md` to a documentation page URL | Retrieve clean context for one page |
| Skill description | [Open `skill.md`](https://docs.o1.exchange/skill.md) | Read the documentation's agent-facing capability summary |
| Documentation MCP | `https://docs.o1.exchange/mcp` | Connect an MCP client to search and retrieve public documentation |
<Note>
The MCP URL is a client endpoint, not a web page. Opening it directly in a browser may return a method-not-allowed response.
</Note>
## Machine-readable production configuration
The [`production-deployments.json`](/launchpad/reference/production-deployments.json) file provides contract addresses, dated configuration, paired assets, fees, governance addresses and contract limits for the supported chains. The [`launch-contract-suites.json`](/launchpad/reference/launch-contract-suites.json) registry identifies current and historical deployments.
See [Stock-paired launches](/launchpad/create/stock-paired-launches) for supported assets, or use the machine-readable [Base](/launchpad/reference/base-stock-quotes.json), [Robinhood](/launchpad/reference/robinhood-stock-quotes.json), [BSC](/launchpad/reference/bsc-stock-quotes.json) and [X Layer](/launchpad/reference/xlayer-stock-quotes.json) stock lists. Standard and Tax use separate factories and paired-asset registrations.
The [Base Tax configuration](/launchpad/reference/base-tax-suite.json), [Robinhood Tax configuration](/launchpad/reference/robinhood-tax-suite.json), [BSC Tax configuration](/launchpad/reference/bsc-tax-suite.json), [Monad Tax configuration](/launchpad/reference/monad-tax-suite.json), [X Layer Tax configuration](/launchpad/reference/xlayer-tax-suite.json) and [Arc Tax configuration](/launchpad/reference/arc-tax-suite.json) list each deployment's contracts, percentage units, claim helper, quote registrations and Dividend exclusions. Use the hosted configuration to resolve a creation-available product route; `currentSuiteIdsByProduct`, where present, identifies the documented product selection. Resolve each Tax deployment by chain and suite, and use the originating factory to identify existing tokens. The JSON separates dated `configuration` observations from the documented `releaseConfiguration`; refresh mutable values from the selected Factory before building transactions. Arc native USDC uses 18 decimals while its shared ERC-20 view uses six; cirBTC uses eight. Resolve the originating suite and reward currency before interpreting event amounts.
These snapshots do not gate the application or Public API. Current creation availability comes from the shared platform catalog together with live quote registration and the active factory's launch-enabled state. Historical entries preserve attribution and original contract bindings. Index-only Tax entries support indexing and direct recovery, not public preparation. Other historical suites retain their documented capabilities; none should be treated as the current creation target.
These JSON files are dated public snapshots that clients can fetch and parse directly. Resolve an existing token using its chain ID and originating factory rather than substituting the current factory. Applications that prepare new creation transactions should also read the current active factory configuration before asking a wallet to sign.
The [Base](/launchpad/reference/base-wsto-suite.json) and [Robinhood](/launchpad/reference/robinhood-wsto-suite.json) \$O launch snapshots identify each chain's burn-only Factory, Hook, settlement reserve, adapter and wstO vault. Their percentage units and immediate quote burns are separate from Standard BPS fees and Tax reward allocations. Use `launch_product=wsto` for [API configuration and preparation](/launchpad/integration/wsto#public-api).
## Public market and launch data
The o1 interface presents:
* launch discovery across All, Crypto, and Stocks views, global search, newest tokens, liquidity, trending, and 24-hour volume;
* token profiles, creators, socials, and explorer links;
* pool price, FDV, liquidity, charts, recent trades, and holders;
* creator announcements and token profile updates;
* Standard creator/referral/platform and Tax creator/protocol/integrator fee-claim information;
* Tax dividend positions, trade-time reward assignment, holder-authorized claims, and burn collection versus delivery.
* per-launch-pool wstO fee-burn totals, separate from global share supply, vault redemptions, reserve funds and recipient revenue.
Contract state and chain events are the authoritative sources for tokens, pools, trades, fees, and claims. The interface adds searchable and historical views around that public data.
## Safe agent workflow
<Steps>
<Step title="Read current information">
Retrieve the relevant documentation, production addresses, and live contract configuration.
</Step>
<Step title="Prepare an unsigned action">
Build the launch, trade, or claim request with the selected chain, creation route, paired asset, current fees, recipients, slippage, and deadline.
</Step>
<Step title="Show the complete result">
Present the contract, assets, amounts, recipients, and expected outcome before requesting approval.
</Step>
<Step title="Sign with the user's wallet">
The user reviews and signs in their wallet. Documentation and data tools never need the private key.
</Step>
</Steps>
Agents and integrations should never store a private key, auto-sign transactions, reuse a stale factory configuration, or infer a creation route from a token symbol alone.
The [BSC stock catalog](/launchpad/reference/bsc-stock-quotes.json) lists all 21 registered bStocks. Its native BNB, USDC and stock quotes use 18 decimals. Stock USD references use TickDB market data with the token's onchain conversion applied once; crypto pricing uses Codex. Canonical launch/trade/fee events remain the source for indexed activity. A deployed catalog does not establish executable routes or complete historical coverage.
X Layer entries include chain 196, native OKB, USDC, xETH and supported wrapped stocks, plus the SwapX router, adapter and release governance addresses. Read the factory for current settings before preparing transactions. Native OKB uses 18 decimals. WOKB provides its same-chain pricing identity while the pool currency remains native OKB. The Public API's supported chain list remains defined by its live `/v1/config` response.
# Direct contract integration
Source: https://docs.o1.exchange/launchpad/integration/direct
Read current launch configuration, build safe launch transactions, trade through Uniswap v4, and co프로젝트로 돌아가기
