Standard launch settings
The retained Standard suites use the fixed-supply and permanent-liquidity model. Their separately dated reference settings below do not describe Tax or $O launch economics:
The platform share of swap fees goes to
0x1cAa...1C90, and the restricted opening-price updater is 0x8BF6...5F29 across the documented configurations. The full addresses are listed in Production contracts.
Standard routes and paired assets
Within Standard, Base, Robinhood, BSC and X Layer each share one factory across crypto and stock creation. Monad and Arc each use one factory for crypto-paired launches. See Stock-paired launches for supported stock pairs on each chain.
Opening assumptions
Each paired asset is configured to target an opening FDV close to USD 4,000. The actual USD opening value depends on the paired asset’s market price and the selected factory’s starting tick.
Opening value
FDV means token price multiplied by the complete fixed supply:Liquidity range
The current configuration places the complete fixed supply into one token-side liquidity range beginning at the opening price. The range boundaries use Uniswap’s spacing value of200, 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, and the platform fee receiver for future launches. The announcement registry is bound once. Every registered paired asset uses per-asset revisions, bounded asset updates, the restricted price updater, and the shared switch for new creation. Integrations should resolve the active factory and read its current values before preparing a transaction. Once a pool opens, its token supply, original creator, paired asset, opening range, fee rates, anti-snipe timing, and permanent liquidity are fixed for that launch. Current creator rights and the destination for future creator-fee credits can change through explicit onchain functions; already credited balances remain with their recorded recipient. Useproduction-deployments.json for exact machine-readable values and Production contracts for explorer-linked addresses.
Monad snapshot
Read on October 1, 2026 at block 109,448,295: owner and creator admin0x5519a8Cc7211F483e19ff8d50A3B0c892701044D, updater 0x8BF6eb1EaA9bE34a068c56945a36a23520705F29, configuration version 15, and creation enabled. MON, USDC and WETH are registered with 18, 6 and 18 decimals. See the Standard snapshot for this factory’s current ticks and revisions. Treasury and fee-policy observations retain their earlier verification dates; read the factory again before signing.
Arc mainnet
Settings for the Arc mainnet contracts. Quote registration, roles, creation status, launch fee and configuration version were reread on October 1, 2026 at block 23,614,087. The fee-policy and router observations retain their September verification dates.
The September 15 fee update succeeded at block
21019549. It set antiSnipeStartTotalBps to 100, equal to baseFeeBps, and antiSnipeWindowSeconds to 1. The creator/platform/referrer components remain 50/30/20 bps with the same IDs, routing rules and recipient addresses. The stored 1-second value is a contract requirement, not an active surcharge period: no extra anti-sniping fee applies at any point. These settings apply to subsequent launches only; existing pools retain their frozen configuration.
The launch fee and any Dev Buy amount are separate from gas. Native and ERC-20 USDC share one balance; integrations must use the correct units for each interface. Arc’s launch governance uses the shared owner, creator-admin, treasury and updater addresses. Read the factory’s current configuration before preparing a transaction.
Both Standard and Tax have registered Circle Wrapped Bitcoin (cirBTC), with 8 decimals at 0x171a4217b86a807a64eb94757db6849fb4bdbaa0. Its starting ticks differ between the two factories; read the selected one. cirBTC uses its own token price without a UI multiplier or fixed-dollar fallback. Native fees remain 18-decimal USDC, and ERC-20 USDC funding remains six decimals. Trading fees and claims for a cirBTC-paired launch use cirBTC units.
BSC mainnet
BSC enables launch creation with a 0.003 BNB fee and 23 registered quotes: native BNB, USDC and 21 bStocks, all with 18 decimals. The attached adapter is0xd94981D2Cac1aBFa9561Fd3F6c0E54357e13E47d. Quote registration and decimals were reread at block 124993313 on October 1, 2026. Read mutable configuration before signing.
The suite uses the standard 1 billion-token, spacing-200, permanent-liquidity model. Its deployment configuration uses a 1% base swap fee split into creator/platform/referrer components of 50/30/20 bps, with a 99% opening total decreasing over 20 seconds. Existing pools retain their own frozen fee settings.
BNB is the zero-address native quote; WBNB is its separate routing wrapper. BSC USDC has 18 decimals, unlike six-decimal USDC on some other chains. Stock display units use each token’s uiMultiplier; pool accounting always uses raw 18-decimal balances. Stock USD estimates use the underlying stock’s reference price and the token’s current conversion multiplier. Opening ticks are stored onchain and must be read independently of current USD estimates.
Owner and creator admin use the shared governance address 0x5519a8Cc7211F483e19ff8d50A3B0c892701044D; treasury is 0x1cAa1962428382106Eb3f29B9719bdF797621C90, and price updater is 0x8BF6eb1EaA9bE34a068c56945a36a23520705F29. Read the factory for current administrative authority.
X Layer mainnet
X Layer uses the same shared governance and fee-recipient addresses as the other chains.
X Layer pairs use native OKB, USDC, xETH or a supported wrapped stock. See the X Layer stock catalog for stock addresses and opening ticks, and the deployment data for paired-asset details.
OKB USD values use WOKB pricing on X Layer, independently of the pool’s native-currency address. Opening ticks affect future launches; market prices and existing pool state evolve separately. There is no fixed-USD or other-chain price fallback.
Removing a quote from new creation does not change existing pools or their fee and claim currencies. See X Layer contracts.
Tax configuration overview
The six Tax configurations use the same owner/creator admin, protocol treasury, inclusive-tax policy and holder-authorized claims. Fees, paired assets, wrappers and custody exclusions remain chain-specific.
Quote registrations, owner/creator-admin roles, creation status and native launch fees were verified on October 1, 2026 against both current factories on every chain. Matching addresses and decimals do not imply matching starting ticks: each factory has its own mutable ticks and revisions. Fee-policy and exclusion observations retain their separate dates below. Additional exclusions are separate from the mandatory exclusions built into each Dividend clone.
Base Tax suite
Base Tax v2 uses its own factory, with the same governance owner, creator admin, protocol treasury and restricted price updater as the Standard v4 suites. The configuration is:
Read the factory before preparing a transaction. The configuration data records the settings and their dated onchain observations.
The supported paired assets are:
- Crypto: ETH, USDC, cbBTC, cbDOGE, cbXRP, cbLTC, cbADA, cbMEGA, cbZEC, cbHYPE, VVV, AERO, MORPHO, Basecat and BLUECHIP.
- Stocks: 51 registered Stock Tokens. See Base Stock Tokens for the complete list and addresses.
base-tax-suite.json for exact addresses, amounts, quote registrations and verification dates.
Factory settings govern future launches. Existing pools retain their frozen taxes, protocol and integrator recipients, Dividend threshold and anti-sniping settings. Creator rights and future creator payouts remain explicitly manageable. The creation switch does not pause existing trading or claims.
Robinhood Tax suite
The deployedrobinhood-mainnet-tax-token-v2 uses the same inclusive policy as Base Tax v2. The configuration follows the shared owner, creator-admin, treasury and updater model used by Base Tax.
All 196 quote addresses and decimals matched Standard minimal-v4 at Robinhood block 76,895,370 on October 1, 2026. Starting ticks differ for some assets. Use the selected factory’s values in the configuration data; registration alone does not prove an optional native-funded Dev Buy route.
The additional Dividend exclusions are Pancake Infinity Vault, O1Staking custody, Ekubo Core and Orvex Vault. Exact addresses are in the snapshot. The Uniswap v4 PoolManager is already a mandatory exclusion in every clone; it does not need an additional default entry. Defaults apply only to future clones. Newly identified pools for existing tokens require a per-launch exclusion; unknown pools are not automatically detected.
Read the factory before preparing a transaction. The configuration data records configuration and dated onchain observations. See Robinhood Tax contracts.
BSC Tax suite
The deployedbsc-mainnet-tax-token-v2 uses the same inclusive policy as Base Tax v2. The configuration follows the shared owner, creator-admin, treasury and updater model used by Base Tax.
All 23 quote addresses and decimals matched BSC Standard minimal-v4 at block 124,993,313 on October 1, 2026. Starting ticks were read independently and differ for some assets. Binance-Peg USDC and all 21 bStocks use 18 decimals. Native BNB uses the zero address; WBNB is the routing wrapper, not a substitute quote address.
The additional Dividend exclusions are Pancake Infinity Vault, Balancer V2 Vault and Ekubo Core. The shared Uniswap v4 PoolManager is already a mandatory exclusion. Defaults apply to future clones only; existing clones need per-launch updates for newly identified pools. Excluding a router or factory does not exclude its pools, and unknown pools may still become eligible.
The configuration data contains quote addresses and starting ticks, exclusion addresses, adapter bindings and dated configuration observations. See BSC Tax contracts.
Monad Tax suite
The deployedmonad-mainnet-tax-token-v2 uses the same inclusive policy as Base Tax v2. The configuration follows the shared owner, creator-admin, treasury and updater model used by Base Tax.
All three quote addresses and decimals matched Monad Standard minimal-v4 at block 109,448,295 on October 1, 2026. Starting ticks were read independently. MON uses 18 decimals and the zero address; USDC uses 6 decimals; WETH uses 18 decimals. WMON wraps native MON; WETH is a separate paired asset. Exact addresses, ticks and revisions are in the snapshot.
Additional Dividend exclusions are Balancer V3 Vault, Ekubo Core, Kuru MarginAccount and Clober BookManager. The Uniswap v4 PoolManager is mandatory separately. Defaults apply only to future clones; existing tokens require per-launch exclusion updates. Unknown pools are not automatically detected.
The router upgrade review supersedes the earlier native-donation blocker for the tested implementations and routes. The October 1 factory readback confirms the shared owner and creator admin. See Monad Tax contracts.
X Layer Tax suite
The deployedxlayer-mainnet-tax-token-v2 uses the same inclusive policy as Base Tax v2. The configuration follows the shared owner, creator-admin, treasury and updater model used by Base Tax.
Both X Layer factories had 48 registered quotes at block 72,040,413 on October 1, 2026: native OKB, USDC, xETH and 45 wrapped stocks. Native OKB uses 18 decimals and the zero address; USDC uses 6 decimals; xETH and the registered wrapped stocks use 18 decimals. WOKB wraps OKB; xETH is a separate quote. The Tax snapshot records its own starting ticks and revisions.
Balancer V3 Vault is the additional Dividend default exclusion. The launch PoolManager is mandatory separately. Defaults apply to future clones; newly identified pools for existing tokens require per-launch updates.
The router upgrade review records approval and local route support for both minimal-v4 and Tax Hooks. See X Layer Tax contracts for contract identities.
Arc Tax suite
arc-mainnet-tax-token-v2 uses the inclusive policy and fee-accrual model with Arc-specific ERC-20 reward payments. The settings follow the shared governance pattern:
Arc native USDC has 18 decimals; its ERC-20 interface has six and exposes the same balance. The launch fee is
2000000000000000000 native units. Starting ticks are -400600 for USDC and -466800 for cirBTC. There is no separate wrapped USDC. Dividend payments and USDC contributions use six-decimal ERC-20 units; cirBTC rewards use eight. Do not sum native and ERC-20 USDC balances. Arc Tax’s optional anti-sniping differs from the Standard suite’s zero-surcharge setting.
Quote registration was reread on October 1, 2026 at block 23,614,087. The Vault exclusion, 0x238a358808379702088667322f80aC48bAd5e6c4, was verified at block 23,158,561 on September 28, 2026. Its pooled-custody identity was reviewed; this is not a claim of an official Pancake deployment on Arc. The launch PoolManager is a separate mandatory exclusion. Defaults apply only to future clones; unknown/token-specific pools require separate review.
See Arc Tax contracts and the snapshot for exact identities and separately dated onchain observations.
Base $O launches
$O launches use a separate Base Factory and burn wstO trading fees. The settings are:
The website uses ETH for Dev Buy. The Public API also supports held wstO. Both support ETH, USDC, $O and wstO for token-page or API trading. See API funding and settlement.
wstO is backed by $O at a changing vault conversion rate. Its opening valuation must use that share value and the registered tick, not assume one wstO equals one $O. Tick updates affect future launches, not existing pools. Reserve capacity, vault conversion and external pool liquidity must also permit the requested transaction.
See contracts and governance and
base-wsto-suite.json. The other tables on this page describe Standard or Tax and do not add their launch fees, treasury or reward settings to wstO.
Robinhood $O launches
Robinhood uses the same burn-only launch model as Base, with its own vault and USDG acquisition route.
The website uses native ETH for Dev Buy; the Public API also accepts held wstO. Token-page and API trading support ETH, USDG, $O and wstO in both directions. USDG has six decimals; the other route assets have 18. Acquisition costs and transaction gas are separate from the launch-pool burn.
The October 8 readback at block 83,108,272 recorded configuration version
10, quote revision 1 and starting tick -117400. These are dated values, not constants for future preparations. Base and Robinhood vault conversions can differ; do not copy a starting tick or assume bridge-driven price equality. Existing pools retain their launch-time burn rates and are not repriced by later opening-tick updates.
See Robinhood contracts and the dated snapshot. The Factory’s live role reads determine governance authority. Full-route simulation checks external liquidity, vault conversion, output protection and settlement inventory independently.
Launchpad of Launchpads configuration overview
Launchpad of Launchpads runs on Base and Robinhood. Each chain has its own registry, vaults and child Tax suite. Both chains use the same values and the shared governance owner and treasury.
The snapshots read both registries and child factories on October 9, 2026, at Base block
52,397,241 and Robinhood block 84,498,331. The snapshots give no evidence that any role address is a multisig or a timelock. The burn destination is the fixed dead address 0x000000000000000000000000000000000000dEaD.
Both registries reserve the same 13 URLs: admin, analytics, api, app, create, docs, o1-exchange, o1exchange, official, staging, swap, trade and www. Nobody can register a reserved URL.
Base Launchpad of Launchpads suite
The deployed child suitebase-mainnet-pads-20261006 and the registry 0x0126...f9Ee use the shared owner, treasury and updater model. The settings are:
Read the registry and the factory before you prepare a transaction. The configuration data records these settings with its dated onchain observations.
The supported paired assets are:
- Crypto: ETH, USDC, cbBTC, cbDOGE, cbXRP, cbLTC, cbADA, cbMEGA, cbZEC, cbHYPE, VVV, AERO, MORPHO, Basecat and BLUECHIP.
1. It did not list wstO. At that block, 0x5519...044D held the registry owner and the child factory owner roles. Registration does not prove pool liquidity or an executable route.
The additional Dividend exclusions are Pancake Infinity Vault, Balancer V2 Vault, Balancer V3 Vault, Ekubo Core, O1Staking custody and the earlier launchpad registry. Each clone also has mandatory exclusions, for example the launch PoolManager. New defaults do not change existing clones.
See Base Launchpad of Launchpads contracts and base-launchpad-suite.json for exact addresses, amounts, quote registrations and verification dates.
Registry and factory settings govern future launchpads and launches. Existing pools keep their frozen taxes, launchpad share and integrator. The owner share of an existing launchpad does not change. No pause stops trading, owner claims or burn claims.
Robinhood Launchpad of Launchpads suite
The deployed child suiterobinhood-mainnet-pads-20261009 and the registry 0x4bFa...3B5F use the shared owner, treasury and updater model. The settings are:
Read the registry and the factory before you prepare a transaction. The configuration data records these settings with its dated onchain observations.
The supported paired assets are:
- Crypto: ETH and USDG.
1. It did not list wstO. The SwapX router approved the child hook. A launchpad token trade also needs wstO settlement inventory. See settlement reserve. Registration does not prove pool liquidity or an executable route.
The additional Dividend exclusions are Pancake Infinity Vault, O1Staking custody, Ekubo Core and Orvex Vault. Each clone also has mandatory exclusions, for example the launch PoolManager. New defaults do not change existing clones.
See Robinhood Launchpad of Launchpads contracts and robinhood-launchpad-suite.json for exact addresses, amounts, quote registrations and verification dates.
Registry and factory settings govern future launchpads and launches. Existing pools keep their frozen taxes, launchpad share and integrator. The owner share of an existing launchpad does not change. No pause stops trading, owner claims or burn claims.
Verification history
The active contracts and mutable configuration were checked onchain on September 2, 2026 at Base block50,751,475 and Robinhood block 51,982,726. Paired-asset registrations and launch settings were reread on September 5, 2026 at Base block 50,902,528 and Robinhood block 54,953,301.
Factory economics and governance were refreshed on September 10, 2026 at Base block 51,134,060 and Robinhood block 59,543,669. Their configuration versions were 13 and 14; the fee settings were unchanged. Those earlier checks remain historical. The current registered-quote lists and factory readbacks were refreshed on October 1, 2026 (UTC+05:30), including a later Base check after Basecat and BLUECHIP were registered. Machine-readable observations retain their exact UTC timestamps:
The review scanned registration events from each factory’s deployment and checked registration, decimals, starting ticks and revisions at the listed block. It does not establish liquidity or executable routes for every asset. Historical suites and their original snapshots are unchanged.