Skip to main content
o1 Launchpad currently charges no token creation fee. Every swap pays a fee in the pool’s paired asset, which becomes claimable by the creator, platform, and valid referrer.

​
Creation fees

The creator still pays the network gas required to confirm the launch transaction. No ETH, stablecoin, or Stock Token approval is needed for a creation fee on any available route under the current configuration.

​
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;
  • 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.

​
First 16 seconds

Trading remains open when the pool launches. The total fee starts at 99% and decreases linearly to the normal 1% fee over 16 seconds. This timestamp-based schedule makes immediate sniping intentionally uneconomic. 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.
o1 uses input-amount swaps: traders enter how much they want to spend or sell, and those swaps remain available throughout the 16-second period. Direct integrations that request an exact output are rejected until the fee reaches 1%.
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 validates it again onchain 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 ignored when it points to:
  • the trader’s connected wallet;
  • the launch creator;
  • the platform fee receiver;
  • an empty or malformed address;
  • the swap router or execution contract.
These checks prevent self-referral and protected-recipient referral. 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.