launchpad-v4-minimal factory for both crypto-paired and stock-paired creation. Base Standard 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.
Base, Robinhood, BSC, Monad, X Layer and Arc Tax have separate launch contracts and configurable trading taxes. Their governance roles follow the same structure as Standard. See the Tax configuration overview for all six configurations and Production contracts for their independently bound addresses.
Who controls what
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;
- Standard base fees, anti-sniping, recipient splits and the platform receiver, or the Tax policy described below.
Tax policy and Dividend administration
For future Tax launches, the owner can change buy/sell bounds, protocol share and clamps, the protocol recipient, anti-sniping opening and duration, and the dividend holding floor. The complete policy can be updated atomically. A zero protection duration allows launches with creator opt-out; it does not by itself disable creation. Existing tokens retain selected taxes, allocation shares, integrator attribution, reward currency, dividend threshold and protection settings. The current creator can change future creator-fund routing through its existing right. Earlier credits do not move. Additional default Dividend exclusions apply only to future clones. Authorized per-launch exclusion/unexclusion and receiver changes affect existing clones. Mandatory system exclusions cannot be removed. Exclusion keeps earned rewards recorded but blocks payment while excluded. Asset recovery can remove backing for unpaid rewards; replenishment restores backing without reallocating those rewards. These powers are part of the trust model, not ordinary creator or holder self-service. See Tax contract integration for the exact functions.$O launch governance
Each chain’s separate $O Factory owner sets buy/sell burn defaults from 0% through 99%, only for future launches. Existing pools keep their rates. There is no creation-fee, payout, allocation or anti-sniping policy to configure. The managed quote registry accepts reviewed burn-compatible ERC-20s; current public support is wstO, not the Standard or Tax quote catalog. Creator rights retain profile and announcement authority without fee-recipient routing. Creator-admin reassignment does not control balances or locked liquidity. The owner, creator admin and price updater use the shared governance addresses. Read the selected Factory to verify current authority before an administrative transaction. The reserve has no independent owner: its authority followsFactory.owner(). That owner can deposit reserve funds, redeem the reserve’s own claims to a specified recipient, or recover direct donations. They cannot withdraw the launch LP position or other accounts’ claims. Full reserve withdrawal is permitted and may make positive-burn swaps fail for insufficient physical inventory. See reserve boundaries.
Adapter replacement changes future atomic-buy execution and requires fresh approvals/configuration. It does not rewrite existing pools. Quote removal or disabling creation stops new launches, not ordinary swaps in existing pools. The vault’s deposit controls and the shared router’s upgrades are separate governance dependencies.
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;
- trading rates, including the buy/sell burn rates for $O launches;
- Standard/Tax allocations and fixed recipients, except that the current creator-fee recipient can change for future credits;
- Standard/Tax anti-snipe start time and duration;
- permanent liquidity position.
Token authority
Tokens launch without an owner who can mint, pause, upgrade, or take balances. Creator rights cover project-side authority, announcements and optional profile editing, plus future creator-fee routing on Standard and Tax. They do not grant control over token transfers or liquidity.Launchpad of Launchpads roles
Each Launchpad of Launchpads registry, on Base and on Robinhood, has its own roles. The shared governance owner and treasury hold these roles. They stay separate contract roles from the Standard and Tax roles.
The registry owner also controls pauses. The registry rejects a renounce of ownership. Ownership moves in two steps: a proposal, then an acceptance.
Two more roles affect launchpads:
- The child Tax factory owner and creator admin keep the Tax suite powers over dividend receivers, holder exclusions and tracker asset recovery. These powers can affect future vault receipts from Tax tokens that a vault holds. They cannot move funds that are already inside a vault.
- The $O launch factory creator admin can reassign the creator rights of a launchpad token. This role belongs to the $O launch product. At the October 9, 2026 reads,
0x5519...044Dheld it on both chains.
Current configuration
The human-readable values are listed in Live configuration. Developers can use the machine-readable production snapshot, review the chain-specific 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 crypto-paired markets 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 the Standard suites on 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. Readowner() and creatorAdmin() to determine current authority. Quote registration, suite selection and launch creation are separate controls. See BSC configuration.