bitpro가 원문에서 글자만 모은 내용이에요. 표·그림·수식은 빠지거나 깨질 수 있어요. 전체 35쪽 중 31쪽
KB market charges OKB;
* a USDC market charges USDC;
* a USDG market charges USDG;
* a stock-paired market charges its selected Stock Token.
For a stock-paired buy, the fee comes from the Stock Token paid. For a stock-paired sell, the fee comes from the Stock Token received.
## Opening anti-snipe period
**Arc Standard has 0% anti-sniping surcharge for launches created after the September 15, 2026 configuration update.** The normal 1% swap fee applies from launch, with creator, platform and referral allocations unchanged. Earlier Arc pools retain their original fee schedule.
<Accordion title="Technical detail: why the contract still stores 1 second">
The contract requires a positive window value, so it stores the minimum of 1 second. This is not an active surcharge period: the opening total fee equals the base fee (both 100 bps), so no extra anti-sniping fee applies at any point.
</Accordion>
On **Base, Robinhood, Monad, BSC and X Layer**, trading remains open when the pool launches. The total fee starts at 99% and decreases linearly to the normal 1% fee over a 20-second window.
The configured schedule on Base, Robinhood, Monad, BSC and X Layer is:
| Time since launch | Approximate total fee |
| -: | -: |
| At launch | 99% |
| 5 seconds | 74.5% |
| 10 seconds | 50% |
| 15 seconds | 25.5% |
| 20 seconds and later | 1% |
The creator and referrer shares are calculated from the normal 1% fee. The temporary amount above 1% is the anti-snipe surcharge and goes to the platform.
Where a surcharge is configured, the optional atomic Dev Buy is the launch-time exception. It pays the normal 1% base fee but not the anti-snipe surcharge. The toggle is off by default, the exemption can be used only inside that launch transaction, and later buys follow the pool's frozen configuration. New Arc Standard pools charge the normal 1% for both the Dev Buy and later trades.
<Note>
o1 uses input-amount swaps: traders enter how much they want to spend or sell, and those swaps remain available throughout the opening period. Direct integrations that request an exact output are rejected while the pool's surcharge window is active. With equal opening and base fees, the Hook treats that window as inactive on new Arc Standard pools. This does not add exact-output support to the o1 interface, Public API, or every router.
</Note>
## Get a referral link
o1 provides two types of referral links:
| Link | Where to copy it | When it applies |
| - | - | - |
| Global referral | Open your profile and select **Referral** | Used as your general referral across o1 Launchpad |
| Token referral | Open a token page, connect your wallet, and select **Referral link** | Applies first to that token on that chain |
The **Profile** link on a profile page is only a public profile link. It does not set referral attribution unless it also contains a referral parameter.
## Which referral is used
For each token, the interface checks referral attribution in this order:
1. a token-specific referral for that exact chain and token;
2. the connected wallet's previously saved global referral;
3. a global referral saved in the current browser.
If the first candidate is invalid, the interface tries the next valid candidate. Opening a token-specific referral link also becomes the global fallback when the visitor does not already have one. Once a wallet has saved a global referral, later global links do not replace it; a token-specific link can still take priority for its exact chain and token.
When a connected wallet first uses a browser-saved global referral, the interface may request a gasless signature to save that attribution to the wallet profile. This is not a token approval or an onchain transaction.
When the trader submits a swap, the interface includes the selected referral address with that trade. `LaunchHook` applies its own onchain reserved-address checks before crediting the referrer's share. An invalid referral never blocks the swap: the hook ignores it and sends the unused referral share to the platform.
## Referral protections
A referral is rejected by the o1 interface or Public API when it points to:
* the trader's connected wallet;
* the original or current launch creator, or the current creator fee recipient;
* the platform fee receiver;
* an empty or malformed address;
* the hook, factory, fee escrow, PoolManager, swap router, or execution contract.
The hook independently rejects the empty address, the v4 executor it sees as `sender`, the current creator, the current creator fee recipient, and its factory, escrow, PoolManager, or hook dependencies. Because a routed swap's onchain `sender` can be an execution contract rather than the trader wallet, direct integrations must enforce the broader trader and platform restrictions before encoding hook data. If no candidate is valid, the trade still works and the referral share goes to the platform.
## Claiming fees
Creator, platform, and referral balances accumulate until claimed. Creators and referrers can open their connected Profile page and use **Fee claims**, where balances are grouped by ETH, stablecoin, or Stock Token. See [Claims](/launchpad/trading/claims) for the complete interface flow and [Functions and events](/launchpad/reference/events-functions) for direct contract integration.
## Tax-token fees
Tax totals include protocol. The remaining allocation goes to creator funds, dividends, burns and any launch-time integrator. Recipient fees and dividends use the paired asset; burns use the launched token. Tax uses the chain-specific creation fees listed above, including 2 native USDC on Arc. See the [launch settings](/launchpad/reference/live-configuration) and [Tax tokens](/launchpad/tax/overview) for examples and optional anti-sniping.
Tax supports public trade comments, but a referral link does not change its frozen integrator attribution.
## \$O launch fees
The Base and Robinhood defaults are 1% buy and 1% sell, charged in wstO and burned during the swap. Pool rates are frozen at launch. There are no creator, platform, referral, integrator or dividend allocations and no anti-sniping surcharge. Ordinary transfers are untaxed. The same burn applies to Dev Buy.
Gas and external ETH/USDC/\$O conversion costs are additional. See [\$O launches](/launchpad/wsto/overview#a-simple-burn-example) for buy/sell examples and supply effects.
## Trade comments
A trader may attach an optional comment of up to 32 UTF-8 bytes. The comment is included with the public onchain trade record. Standard includes referral attribution; \$O trades record their burn amount without a referrer. Integrators must use the [suite-specific Hook data](/launchpad/integration/wsto#hook-data).
# Single-sided liquidity
Source: https://docs.o1.exchange/launchpad/trading/liquidity
How the opening value, token-only liquidity, changing pool inventory, and permanent Uniswap v4 market work.
Every launch opens a real Uniswap v4 pool. All tokens available to the market begin on the token side of the opening price, so the creator does not need to deposit ETH, OKB, USDC, USDG, a Coinbase crypto major, or a Stock Token as liquidity.
## Current market setup
| Setting | Current value |
| - | - |
| Pair | Launch token and the creator's selected paired asset |
| Opening value | FDV close to USD 4,000 under the current quote assumptions |
| Pool supply | Complete fixed supply |
| Liquidity | One continuous token-side range beginning at the opening price |
| Range share | 100% of the pool supply |
| Position owner | The suite's launch Hook |
| Removal | Permanently disabled |
The liquidity range uses Uniswap's spacing value of `200`. This controls where the range can begin and end; it does not force prices or trades to move in fixed steps.
## Opening FDV
Current launches have a fixed supply of **1 billion (1,000,000,000) tokens**. The opening FDV is the opening token price multiplied by that complete supply.
| Quote assumption | Current opening target |
| - | - |
| ETH, MON, BNB, OKB or WETH at the current factory-managed opening reference | FDV close to USD 4,000 |
| USDC at USD 1 | FDV close to USD 4,000 |
| USDG at USD 1 | FDV close to USD 4,000 |
| Supported Stock Token at its configured reference price | FDV close to USD 4,000 |
| wstO using \$O's reference price and the current vault conversion | Opening valuation depends on the registered wstO tick and current share value |
FDV is a valuation reference, not money raised or deposited. Its USD value changes with the paired asset's market price. Paired-asset price references can update the opening setting for future launches without changing an existing pool. Trading moves each live token price according to its own Uniswap v4 market activity.
## How inventory changes
<Steps>
<Step title="The market opens with tokens">
The permanent position starts with the pool supply in launch tokens and no paired-asset deposit from the creator.
</Step>
<Step title="Buys add the paired asset">
Buyers send the selected paired asset, such as ETH, OKB, USDC, USDG, a supported Coinbase crypto major, or a supported Stock Token, and receive launch tokens. Launch-token inventory decreases while paired-asset inventory increases.
</Step>
<Step title="Sells return tokens">
Sellers send launch tokens back to the pool and receive the paired asset at the live Uniswap v4 price.
</Step>
<Step title="The position stays active">
Remaining launch tokens and the accumulated paired asset continue supporting the market inside the same permanent position.
</Step>
</Steps>
Because the position starts with launch tokens and no paired-asset inventory, early sell quotes depend on assets added by earlier buys. A sell may be limited or unavailable until the pool has enough native currency, stablecoin, crypto-major, or Stock Token inventory to return.
```text theme={null}
pool supply = 1,000,000,000 tokens
```
## Token-only launch check
Before the launch completes, the contracts verify that opening the position requires launch tokens only. If a configuration would require native currency, a stablecoin, a crypto major, or a Stock Token from the creator, the transaction stops.
## Why liquidity is permanent
* the suite's launch Hook owns the position;
* its liquidity cannot be decreased or removed;
* outside accounts cannot modify the locked position or add their own liquidity in that launch pool;
* there is no transferable LP token or position NFT;
* there is no administrator withdrawal or recovery path.
The assets remain inside Uniswap. o1 can adjust settings for later launches but cannot remove or rewrite an existing position.
## Tax tokens and other pools
Tax on Base, Robinhood, BSC, Monad, X Layer and Arc preserves the same liquidity lock and zero LP fee in its launch pool. Its creator/dividend/burn/integrator allocations do not include automatic liquidity provision. Tax burn delivery removes collected tokens from usable circulation; it does not add liquidity or guarantee a price increase.
These restrictions apply to the launch pool. Other people can create separate pools, but trading there does not automatically contribute to the launch token's taxes. See [dividend eligibility](/launchpad/tax/dividends#exclusions-and-administration) for how pool-held tokens affect rewards.
<span />
## \$O launch liquidity
\$O launches retain the same locked, token-only position and zero launch-pool LP fee. The burn reduces wstO supply, not launched-token supply. It does not add liquidity or mechanically increase the pool price.
The settlement reserve is separate from the locked launch position. It provides temporary physical inventory for immediate burns before a router settles its input. Its owner can redeem only the reserve's own claims, not withdraw the launch LP position. Insufficient inventory reverts the affected transaction; a reserve deposit cannot fix an illiquid external ETH/USDC/\$O conversion pool. See [settlement accounting](/launchpad/integration/wsto#settlement-reserve).
# How it works
Source: https://docs.o1.exchange/launchpad/wsto/overview
Launch a token paired with wstO, backed by $O, with trading fees that burn wstO immediately.
**\$O launches** create a fixed-supply ERC-20 token paired with **wstO** on Base and Robinhood. Buy and sell fees burn wstO during each trade, reducing its total supply while leaving its underlying \$O backing in the vault.
wstO is the paired asset, not the token you create. Your launched token keeps its fixed supply and permanent Uniswap v4 liquidity.
Create an \$O launch on **Base or Robinhood** through the [website](/launchpad/create/token-creation) or [Public API](/launchpad/api/launches#o-launches).
## How it differs from Standard and Tax
| Feature | Standard | Tax | \$O launches |
| - | - | - | - |
| Trading charge | Configured fee sharing | Creator-selected inclusive taxes | Pool's fixed buy/sell wstO burn rates |
| Fee destination | Creator, platform and referrer | Protocol plus selected allocations | Entire suite trading fee is burned |
| Burn asset | No built-in burn allocation | Launched token | wstO paired asset |
| Burn timing | Not applicable | Collected tokens sent to a dead address separately | Actual supply burn in the swap transaction |
| Dividends or fee claims | Recipient fee claims | Recipient claims and optional dividends | None from this suite |
| Anti-sniping surcharge | Chain-specific | Optional at launch | None |
| Base / Robinhood creation fee | 0.001 ETH | 0.001 ETH | None; network gas still applies |
| Ordinary wallet transfers | Untaxed | Untaxed | Untaxed |
The default burn rates are **1% on buys and 1% on sells**. See the [Base](/launchpad/reference/live-configuration#base-wsto-suite) and [Robinhood](/launchpad/reference/live-configuration#robinhood-wsto-suite) launch settings. Governance can change the defaults for future launches within 0% to 99%. Each pool permanently keeps the rates set when it launches; creators do not choose an allocation or fee recipient.
External conversion pools can charge their own fees. Network gas and any upstream protocol charges are separate from the suite's burn fee.
## What is wstO?
wstO is an ERC-20 share token backed by \$O held in its vault. The vault and the wstO token use the same address within each chain: see [Base](/launchpad/reference/production-contracts#base-wsto-contracts) and [Robinhood](/launchpad/reference/production-contracts#robinhood-wsto-contracts).
* **Deposit \$O:** the vault receives \$O and issues wstO at its current conversion rate.
* **Redeem wstO:** the vault destroys the redeemed shares and returns the corresponding \$O. There is no withdrawal cooldown in this integration.
* **Burn a trading fee:** the launch Hook destroys the wstO it collected, without withdrawing \$O.
Do not assume that one wstO always equals one \$O. Use the current vault preview for the amount being converted. Deposits can be paused by the vault's separate governance, and conversion limits, rounding and transaction deadlines still apply.
This backing vault is different from the optional [staking reward vaults](/launchpad/staking/overview). Creating an \$O launch does not create a new backing vault or staking program.
## A simple burn example
At a 1% buy rate, a buy spending **100 wstO** burns **1 wstO** and uses **99 wstO** for the launch-pool purchase. The buyer receives the resulting launched tokens.
At a 1% sell rate, if selling launched tokens produces **100 wstO** before the burn fee, **1 wstO** is burned and the seller receives **99 wstO**. A route paying the seller in \$O, USDC, USDG or ETH then converts that remaining wstO.
These are exact-input examples before any separate route costs. Integer rounding applies, so a tiny fee can round to zero. The final quote includes the route's conversion, burn and slippage protection.
Only swaps through the suite's launch Hook contribute to this mechanism. Wallet transfers, centralized exchanges and separate pools do not automatically burn wstO for this suite.
## Create and buy
Choose **\$O** on Base or Robinhood in the [Create flow](/launchpad/create/token-creation): enter a name, symbol, image and optional profile details, then review the wstO pair and burn rates.
The current factory creates **1 billion tokens with 18 decimals**. All of them seed permanently locked, token-only liquidity. Plain creation requires gas but no creation fee, wstO deposit or initial purchase.
The optional website **Dev Buy** uses ETH:
| Chain | Atomic Dev Buy |
| - | - |
| Base | Create token and pool → ETH → USDC → \$O → wstO → new token → creator |
| Robinhood | Create token and pool → ETH → USDG → \$O → wstO → new token → creator |
The \$O-to-wstO step deposits into the vault on the selected chain. No bridge is involved in the launch transaction.
The router handles native wrapping within the acquisition route. You do not need to hold or approve wstO for this ETH-funded flow. Leave additional ETH for gas. The normal buy burn applies to the actual wstO entering the launch purchase, not to the original ETH amount.
Creation and the purchase are one atomic transaction. A failed conversion, incomplete input spend, insufficient output or failed burn reverts the whole launch. You can choose a smaller Dev Buy or launch without one; increasing slippage cannot fix unavailable liquidity or a failed vault operation.
The Public API also accepts wstO already held in your wallet for Dev Buy. See [funding and approvals](/launchpad/api/launches#atomic-dev-buy). The [o1 Bot V1 flow](/launchpad/bot/quickstart) is limited to Standard crypto-paired Base launches.
## Trading after launch
The token page and Public API support these payment and receipt assets:
| Pay with or receive | Base | Robinhood |
| - | - | - |
| wstO | Direct launch-pool trade | Direct launch-pool trade |
| \$O | Deposit for wstO, then trade | Deposit for wstO, then trade |
| Stablecoin | USDC → \$O → wstO → token | USDG → \$O → wstO → token |
| ETH | ETH → USDC → \$O → wstO → token | ETH → USDG → \$O → wstO → token |
Sells reverse these paths, including vault redemption and native ETH delivery when selected.
The pool is always paired with wstO. Selecting ETH, USDC or USDG changes your payment or receipt asset, not the pool's paired asset. Sells through the vault redeem the net wstO after the burn, using the resulting vault state. Approve only the spender shown for the selected route. Native ETH inputs need no ERC-20 approval; token inputs and sells may require one.
Each quote checks the entire route at the requested size. Acquisition-pool liquidity, launch-pool liquidity, the vault and the [settlement reserve](/launchpad/integration/wsto#settlement-reserve) are separate constraints. A larger trade can fail even if a smaller one works.
## Price, supply and burn totals
Burning shares can increase the \$O backing per remaining wstO share. For example, 100 \$O backing 100 wstO becomes 100 \$O backing 99 wstO after a one-wstO fee burn, before any other activity.
This **does not burn \$O or guarantee a higher market price**. \$O's price can fall, deposits and redemptions change supply, and executable prices depend on pool liquidity and demand. The launch pool prices your new token against wstO; reducing wstO's global supply does not automatically change that pool's price or add liquidity.
The displayed wstO USD price uses \$O's reference price and the vault conversion on the selected chain. Each chain has its own vault conversion rate, so wstO share values can differ. It is a reference valuation, not a guaranteed sale price. Supply comes from the token contract. Liquidity and top-market estimates depend on available market data; missing coverage is not proof of zero liquidity.
**Total wstO burned** on a launched token's page means the accumulated confirmed fee burns from **that token's launch pool**. It is not the total across every launch, every voluntary burn or vault redemptio프로젝트로 돌아가기
