Skip to main content
These are the current onchain settings for new launches, checked on July 28, 2026.

Current launch settings

Both production chains currently use the same core settings: The platform share of swap fees goes to 0x1cAa...1C90. The full address is listed in Production contracts.

Routes and paired assets

The Base stock suite is not listed as a current creation route because no Base stock catalog is published yet. It can appear automatically after catalogued assets are registered on the live factory and creation is enabled. Robinhood’s current 96-token catalog is listed in Stock-paired launches.

Opening assumptions

Each paired asset is configured to target an opening FDV close to USD 4,000. The actual USD value of an ETH or stock-paired launch changes with the paired asset’s market price.

Opening value

FDV means token price multiplied by the complete fixed supply:
It is a valuation reference. It is not money raised, paired assets deposited by the creator, or a guaranteed future price.

Liquidity range

The current configuration places all pool supply into one token-side liquidity range beginning at the opening price. Pool supply means the fixed token supply minus any immediate and vested allocations. The range boundaries use Uniswap’s spacing value of 200, which is about 2.02% between places where a range boundary may be set. This does not make trades or prices move in 2.02% jumps; trading moves continuously through the active liquidity.

Values that can change

Governance may update supply, supported paired assets, opening settings, creation fees, liquidity settings, swap fees, the platform fee receiver, and announcement support for future launches. Stock routes also support per-quote revisions, bounded quote batches, a restricted price updater, and a switch for new stock creation. Integrations should read these values from the selected route’s current factory before preparing a transaction. Once a pool opens, its token supply, creator, paired asset, opening range, fee settings, anti-snipe timing, allocations, vesting, and permanent liquidity are fixed for that launch. Use production-deployments.js for exact machine-readable values and Production contracts for explorer-linked addresses.