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

Contract hard caps

The supply caps assume the launch token’s standard 18 decimals.

Token fields

Creator profile fields

Creator-profile changes use a wallet signature and affect the public o1 profile only. They do not change token permissions, balances, or liquidity.

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. Base currently has four registered Stock Tokens from a 13-asset catalog, and Robinhood has 194 registered Stock Tokens. Every stock-paired launch token must have an address ending in 01, and a stock quote’s opening frame must remain aligned with the active tick spacing. Price updates use per-quote revisions so stale writes fail.

Staking vault limits

When early withdrawal is forbidden, the configured penalty must be zero. When it is allowed, a zero penalty provides a penalty-free early exit. Each deposit creates a separate lot. The interface supports partial withdrawals, withdrawing from several lots together, and claiming multiple completed epochs together. Staking accepts B20 and ERC-20 assets only when their balances change by the exact transferred amount. Fee-on-transfer, rebasing, reflection, and other non-standard balance behavior is unsupported. See the staking guide for the complete lifecycle.

Transaction checks

A launch stops when the selected paired asset or creation route is unavailable, the payment is wrong, stock creation is disabled, the address suffix is invalid, the transaction has expired, protected settings differ from the values the creator reviewed, 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.