Standard defaults
Standard contract hard caps
The supply caps assume the launch token’s standard 18 decimals.
Standard fee and referral rules
- every configured fee component must be valid and all component bps must add up exactly to the base fee; the current configuration uses creator, platform, and referrer components;
- 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 o1 interface and Public API reject the trader, original or current creator, current creator fee recipient, platform fee receiver, empty address, and protocol or execution dependencies as referrers;
- the hook independently rejects the empty address, the v4 executor, current creator, current creator fee recipient, hook, factory, fee escrow, and PoolManager; direct integrations must apply the broader product restrictions themselves;
- the unused referral share goes to the platform.
Tax-suite limits
If bounds permit exactly zero, that side has no ordinary fees even with a positive protocol floor. Positive totals below the floor reject. A zero allocation earns no rounding residue. Each configured minimum must be compatible with its maximum and protocol floor. Existing launches keep their frozen values after policy changes.
Tax retains the 18-decimal supply bounds, locked liquidity, 64-entry quote batches and 4,096-byte atomic route-data cap. It has no Standard fee-component list or financial referral fallback. See exact Tax rules and the dated policy.
$O launch limits
Zero and rounded-zero burns still produce trades. A positive exact-output fee rounds up and can consume one raw unit on a dust-sized request. The valid percentage range does not guarantee sufficient inventory or output. See burn mathematics.
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.
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. The October 1, 2026 quote verification covers both current Standard and Tax factories. Base has 15 crypto quotes and 51 Stock Tokens; Robinhood has ETH, USDG and 194 Stock Tokens; BSC has BNB, USDC and 21 bStocks; X Layer has OKB, USDC, xETH and 45 wrapped stocks. Monad supports MON, USDC and WETH. Arc registers six-decimal ERC-20 USDC and eight-decimal cirBTC, with launch fees paid in 18-decimal native USDC. Registration is separate from route liquidity and current availability. For X Layer atomic Dev Buy into a non-native quote, the attached adapter must advertise native-V3 support and an executable acquisition route must exist. See route prerequisites. Every token from a current factory must have an address ending in01. A managed 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.
Launchpad of Launchpads limits
The Tax hook gives the vault launch check a fixed gas budget of 50,000. The vault check never reverts. If the check fails, the launch can complete without membership. See How the launchpad accepts a token.