Configuration and governance

What o1 governance can change for future launches and which properties remain permanent after a token launches.

Base, Robinhood, BSC and X Layer each use one active launchpad-v4-minimal factory for both crypto-paired and stock-paired creation. Base creates native B20 tokens, while Robinhood, Monad, Arc, BSC and X Layer create fixed-supply ERC-20 tokens. A catalogued paired asset becomes available when it is registered on the active factory and creation is enabled. Available market types share the same launch model, fee system, creator rights, announcements, and permanent Uniswap v4 liquidity.

Who controls what

Area	Current authority	Boundary
Future launch settings	Launchpad governance owner	Changes apply only to launches created afterward
Platform swap fees	Platform fee receiver	Receives its share but cannot control tokens or pools
Paired-asset opening-price updates	Restricted price updater	Can update future opening frames only; cannot register assets, change fees, or modify pools
Creator rights	Current creator	Can transfer creator rights and change the destination for future creator-fee credits; receives no token or liquidity control
Creator-rights administration	Creator admin	Can immediately reassign current creator rights and future creator-fee routing; receives no token or liquidity control
Token profile editing	Current creator, only when enabled at launch	Limited to supported profile information
Announcements	Current creator	Can publish updates but receives no token or liquidity control
Permanent liquidity	Launch hook	Cannot be removed, transferred, or redirected

The current governance owner and platform fee receiver are listed in Production contracts.

Settings for future launches

Governance can update these defaults:

• supported paired assets and any future creation fees;
• the opening price used for each paired asset;
• fixed token supply within the contract caps;
• liquidity range settings;
• the base fee, anti-snipe fee, recipient split, and platform fee receiver.

The announcement registry is bound once and cannot be replaced.

All six current factories include a creation switch, bounded paired-asset updates, and per-asset revisions. The owner can register or remove paired assets. The restricted updater can change only the opening-price frame of an already registered asset, using its latest revision. Each factory’s creation switch and global native launch fee apply to all its supported quotes. Monad and Arc support the standard crypto route only.

The interface refreshes the current settings before a creator signs. If protected global settings change while a prepared transaction is pending, the transaction stops instead of silently using different economics. A paired asset’s opening-price refresh intentionally applies the latest registered frame when the launch executes.

What becomes permanent

When a launch succeeds, the following properties are fixed for that launch:

• token address and total supply;
• original creator and selected paired asset;
• market type and launch contracts;
• opening pool and liquidity range;
• fee component rates and fixed recipients, except that the current creator-fee recipient can change for future credits;
• anti-snipe start time and duration;
• permanent liquidity position.

Future governance changes cannot mint more tokens or remove liquidity. A valid creator-rights transfer can update the current creator and future creator-fee recipient. Already credited balances do not move.

Token authority

Tokens launch without an owner who can mint, pause, upgrade, or take balances. Creator rights cover project-side authority, future creator-fee routing, announcements, and optional profile editing. They do not grant control over token transfers or liquidity.

Current configuration

The human-readable values are listed in Live configuration. Developers can use the machine-readable production snapshot, review the Base and Robinhood catalogs in Stock-paired launches, and refresh changeable values from the route-selected active factory before preparing a transaction.

Monad scope

Monad uses the same managed configuration and creator-rights model, with a standard crypto route only. Its owner, creator admin and treasury use the shared governance addresses. Read the factory’s current configuration before preparing a launch.

Arc scope

Arc uses the same governance methods and shared owner, creator-admin, treasury and updater configuration as Base and Robinhood. Treasury changes apply to subsequent launch-fee payments and new pools; existing pool recipients and accrued claims remain unchanged. See Arc configuration for current launch settings.

BSC scope

BSC shares one managed factory across crypto and stock routes. Its owner and creator admin use the shared governance address; treasury and updater use the shared addresses as well. Read owner() and creatorAdmin() to determine current authority. Quote registration, suite selection and launch creation are separate controls. See BSC configuration.

X Layer scope

The X Layer release configuration uses enabled creation and the same governance, creator-admin, treasury and updater addresses as the other chains. The owner and creator-admin handovers take effect when the pending recipient accepts them. Supply, permanent liquidity, quote revisions and creator-rights behavior follow the same minimal suite. See X Layer configuration.