Skip to main content
Every launch pays the current global native creation fee, and every swap pays a fee in the pool’s paired asset. Swap fees become claimable by the creator, platform, and valid referrer.

​
Creation fees

The creator also pays the network gas required to confirm the launch transaction. Each active factory uses one global native fee for every quote: 0.001 ETH on Base/Robinhood, 100 MON on Monad, 2 native USDC on Arc, 0.003 BNB on BSC, and 0.02 OKB on X Layer. A USDG-paired Robinhood launch does not pay its creation fee in USDG. Creation fees are mutable settings for future launches. Read the active factory immediately before preparing a transaction. Arc uses 18-decimal native USDC for the launch fee. Trading fees and claims use the selected pool quote: six-decimal ERC-20 USDC or eight-decimal cirBTC. Only native and ERC-20 USDC share one balance; cirBTC is a separate asset. Its configured swap fees have no anti-snipe surcharge for new launches; the normal 1% trading fee still applies.

​
Normal swap fee

The normal swap fee is 1% of the paired-asset amount. With a valid referrer, that 1% is divided as follows: If a trade has no valid referrer, the unused 0.2% referral share goes to the platform. Fees are always denominated in the selected paired asset:
  • an ETH market charges ETH;
  • an OKB 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 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.
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.
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: 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 pools charge the normal 1% for both the Dev Buy and later trades.
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 pools. This does not add exact-output support to the o1 interface, Public API, or every router.
o1 provides two types of referral links: 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.

​
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, together with the direction, paired asset, referrer, and fee.

​
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 for the complete interface flow and Functions and events for direct contract integration.