Integration sequence
1
Select the active route
Resolve the current factory by chain and route. Use the crypto factory for ETH, USDC, or USDG, and the stock factory for a supported Stock Token. Do not infer the route from a symbol.
2
Read launch configuration
Read
configVersion, launchSupply, tickSpacing, feeDefaults, bands, and quotes(selectedQuote) at one recent block. For a stock factory, also read launchCreationEnabled, nativeLaunchFee, and quoteRevision(selectedQuote).3
Validate parameters
Apply the hard limits in Limits and validation, confirm the quote remains registered, and calculate the pool supply after allocations.
4
Build payment
Creation is currently free, so the production transaction sends no launch fee. Still read the route’s live fee field: standard factories use
quotes(selectedQuote).creationFee, while stock factories use nativeLaunchFee. If governance later sets a non-zero value, follow the active factory’s exact currency rule.5
Commit to the configuration
Set
expectedConfigVersion to the fresh read and choose a short chain-time deadline. The o1 Launchpad interface uses the latest block timestamp plus 30 minutes. Stock tick-only updates advance the selected quote revision without changing the global version, so execution intentionally uses the latest registered opening frame.6
Simulate, sign, and confirm
Simulate
createLaunch, present all recipients and economics to the user, then request a wallet signature and wait for a successful receipt.7
Parse canonical events
Read
Launched for token and pool ID, then index the other factory, hook, PoolManager, escrow, vesting, and announcement events from the same transaction. For trades, derive direction and wallet attribution from the complete receipt rather than treating Trade.executor as the user’s address.Read the current snapshot with viem
The example below reads the Base crypto factory. For another route, use its current factory and paired-asset addresses from Production contracts.LaunchParams contains nested vesting arrays, so a partial handwritten write ABI is easy to get wrong.
startTickToken0Frame is the factory’s internal opening-price encoding for a registered quote. The factory handles token ordering and tick spacing when it creates the pool; a launch transaction selects the quote and does not submit a starting tick.
Stock-route reads
Add these reads when the selected pair belongs to a stock suite:1. Robinhood stock launches must prepare the finalized token metadata first, read launchTokenBytecodeHash, and mine a salt whose predicted ERC-20 address ends in 01. Base B20 addresses can be predicted before signing through the B20 creation formula.
LaunchParams
Trading integration
Launch pools are ordinary Uniswap v4 pools with a required hook. Use the listed v4 Quoter for price discovery and the Universal Router plus Permit2 for execution. Preserve the exact pool key: sorted currencies, LP fee0, launch tick spacing, and the hook address frozen into that launch’s contract suite.
tickSpacing is part of the exact Uniswap pool identifier and controls valid liquidity range boundaries. The current value 200 represents about 2.02% between allowed boundaries; it does not make swap prices move in fixed 2.02% increments.
Use exact-input during the anti-snipe window. Encode optional hook data as the referrer address followed by a bytes32 comment. Simulate at current timestamp and include slippage and deadline protection. Current pools charge hook fees in the paired asset, including the selected Stock Token for stock-paired markets.
Failure handling
For user launches, treatStaleConfig and LaunchExpired as refresh-and-rebuild errors. StaleQuoteRevision applies to restricted stock opening-price updates, not to launch submission. Treat quote removal, disabled stock creation, fee mismatch, invalid 01 suffix, allocation validation, salt reuse, immutability, and single-sided failures as blocking errors that require changed inputs or configuration. Do not silently fall back to another factory, route, or quote.