Skip to main content
The interface checks launch inputs before the wallet asks for a signature. The contracts enforce the hard caps again onchain.

Current defaults

SettingCurrent value
Supply1 billion (1,000,000,000) tokens
Liquidity ranges1
Base swap fee1%
Starting total fee99%
Anti-snipe period16 seconds
Base-fee split50% creator / 30% platform / 20% referrer

Contract hard caps

ConstraintHard limit
Token supply1 million to 1 trillion tokens
Immediate plus vested recipients128 total
Vested beneficiaries64
Vesting steps per beneficiary24
Vesting steps across one launch128
First vesting unlockAt least 1 day after launch
Liquidity ranges1 to 10
Base swap feeAt most 10%
Starting total feeAt most 99%
Profile authority choiceFixed profile or editable profile
The supply caps assume the launch token’s standard 18 decimals.

Token fields

FieldInterface limit
Name50 characters
Symbol11 characters with no spaces
Image2 MB; PNG, JPG, WEBP, or GIF
WebsiteValid website URL
XValid X profile URL
TelegramValid Telegram link
Extra informationNon-empty keys with public values
Trade comment32 UTF-8 bytes

Creator profile fields

FieldInterface limit
Display name40 characters
Bio180 characters
Avatar2 MB; PNG, JPG, WEBP, or GIF
WebsiteValid website URL
XValid X profile URL
TelegramValid Telegram link
Creator-profile changes use a wallet signature and affect the public o1 profile only. They do not change token permissions, balances, or liquidity.

Allocation and vesting rules

  • every amount must be greater than zero;
  • a recipient can appear only once across immediate and vested allocations;
  • allocations must leave at least some supply for the market;
  • vesting dates must strictly increase;
  • each step must release a positive percentage;
  • all step percentages must add up to exactly 100%;
  • the first unlock must be at least one day after launch;
  • each step must release an additional token amount after rounding;
  • locked tokens always pay the beneficiary recorded at launch.

Fee and referral rules

  • creator, platform, and referrer shares must add up to 100% of the base fee;
  • the starting total fee cannot be lower than the normal base fee;
  • the anti-snipe period must be longer than zero;
  • the platform fee receiver must be a valid address;
  • the trader, creator, platform fee receiver, empty address, and swap router or execution contract cannot receive referral credit for that trade;
  • the unused referral share goes to the platform.

Quote requirements

Only quote currencies registered by o1 governance can be selected. Quote tokens must behave like standard ERC-20 tokens. Transfer-tax, rebasing, and other non-standard balance behavior is not supported because it can break pool and fee accounting.

Transaction checks

A launch stops when the selected quote is unavailable, the payment is wrong, the transaction has expired, current settings differ from the values the creator reviewed, recipients or vesting are invalid, or the pool cannot open with token-only liquidity. Developers who need the exact encoded caps and field names can use Functions and events and the machine-readable production snapshot.