Smart contract architecture

How the launch factories, launch hook, fee escrow, staking contract, announcement registry, and launch tokens work together.

Base, Robinhood, Monad, Arc, BSC and X Layer use the same launchpad-v4-minimal architecture for launch coordination, permanent liquidity, fees, creator rights, announcements, and optional atomic Dev Buy. The chain-specific token step differs: Base creates and validates a native B20 token, while Robinhood, Monad, Arc, BSC and X Layer create a fixed-supply ERC-20 through a dedicated token deployer. Each contract has a narrow responsibility, which makes its authority and custody easier to verify.

Arc uses the same ERC-20 core with an adapter for native and ERC-20 USDC.

Launch path

The creator signs one factory transaction. It creates the token, opens the Uniswap v4 pool, and places the complete fixed supply into the permanent liquidity position.

Trading path

The trader signs a swap through Uniswap. The launch hook applies the fee, the user receives the trade output, and the fee escrow records claimable balances.

Staking path

A vault creator funds an independent reward program. Participants approve and deposit wallet-held tokens, then withdraw principal and claim completed-epoch rewards under the vault’s fixed rules.

Contract responsibilities

Contract	Responsibility	Custody or authority
Launch factory	Coordinates crypto-paired and stock-paired launches on its deployed chain	Controls future launch settings, paired assets, creator rights, and the global native launch fee on that chain
Base token validator	Verifies each created B20 token’s supply, policy, roles, and profile-authority boundary	Stateless and called by the Base factory; holds no user funds
ERC-20 token deployer	Creates the fixed-supply ERC-20 for its bound launch factory	Callable only by that factory; holds no user funds
Launch hook	Opens approved pools, owns permanent positions, and applies swap fees	Owns and permanently locks launch liquidity positions
Fee escrow	FeeEscrow records and pays each recipient’s swap-fee balance	Can pay only balances credited by the hook
Launch-buy adapter	Executes the optional atomic buy after the selected factory creates and seeds a launch; Arc uses ArcSwapXLaunchBuyAdapter for USDC funding	Each deployment is bound to its chain’s factory, hook, PoolManager, and supported routing path
Staking contract	Stores fully funded reward programs and participant principal	Holds accounted principal and rewards; its owner controls only the fee for future vault creation
Announcement registry	AnnouncementRegistry publishes creator-authenticated announcements	Has no token authority and holds no funds
Robinhood / Monad / Arc / BSC / X Layer token	LaunchToken is the fixed-supply ERC-20 implementation	Has no owner or administrative control

Factory: launch coordination

createLaunch coordinates the complete launch. The selected chain determines the production factory, and the paired asset determines the market type. Base, Robinhood, BSC and X Layer each use one active factory for both crypto-paired and stock-paired launches.

The minimal factories also expose createLaunchAndBuy. It creates the token, opens and seeds the pool, then executes one protected buy through the chain’s configured adapter in the same transaction. An ordinary launch continues to use createLaunch. Both methods require creation to be enabled.

Stage	Factory behavior
Validate	Confirms the selected paired asset, route, current creation fee, deadline, profile-editing choice, and launch limits
Create token	Creates the fixed supply and verifies the expected immutable token properties
Configure market	Records the original creator, current creator fee recipient, frozen fee components, anti-snipe schedule, currencies, and exact pool identity with LaunchHook
Open pool	Initializes the Uniswap v4 pool at the configured opening price
Seed liquidity	Sends the complete fixed supply to the permanent position owned by the hook
Publish result	Emits the token address, creator, pool ID, quote, supply, and spacing in Launched

The factory owner may update paired assets, supply, opening prices, liquidity ranges, fees, and the platform fee receiver for future launches. The announcement registry is bound once and cannot be replaced. The minimal factories provide bounded paired-asset updates, revision checks, a restricted opening-price updater, and a switch for new creation. That switch covers every new launch through the factory, regardless of paired asset. These changes cannot rewrite a completed token or pool.

Launch-buy adapter

The browser prepares SwapX route data, while SwapXLaunchBuyAdapter enforces the atomic Dev Buy boundary onchain. The adapter is not a quote engine. It accepts calls only from the configured launch hook, checks that the route starts with the actual funding asset, requires connected non-cyclic hops, and requires the final hop to use the exact newly created launch pool, selected paired asset, launch token, and hook. Routes are bounded to four hops, external pools must match the venues permitted by that deployment, and the creator must receive at least minAmountOut. The transaction also stops if it changes any unexpected route-asset or native-currency balance held by the adapter or SwapX router.

Venue support is deployment-specific without changing the factory or UI flow. The active Base adapter uses its configured v3 and Aerodrome path. The active Robinhood adapter can also validate constrained external v4 pools through its configured PoolManager. For these adapters, the complete launch reverts if the optional buy cannot satisfy the route and output checks; ordinary createLaunch remains independent.

Managed paired-asset controls

Each active factory keeps its chain’s native asset, supported stablecoin, registered crypto majors where configured, and registered Stock Tokens in one paired-asset registry. Every asset has its own availability state, decimals, opening-price frame, and revision.

Control	Purpose
Quote registration	Adds a supported paired asset and its opening-price frame
Quote revision	Prevents a stale price update from overwriting a newer one
Price updater	May update the opening frame of an existing quote, but cannot add or remove assets or change fees
Creation switch	Pauses new launches through that factory; existing pools continue trading and claiming
Batch limit	Bounds one quote-management transaction to 64 entries

At the September 5 quote snapshot, Base had 20 registered quotes in the shared factory: ETH, USDC, eight Coinbase crypto majors, and ten stock quotes listed in the Base stock catalog. The crypto majors are cbBTC, cbDOGE, cbXRP, cbLTC, cbADA, cbMEGA, cbZEC, and cbHYPE. The ten registered Base stock quotes come from a 13-asset catalog. Robinhood had ETH, USDG, and 194 registered stock quotes. The platform requires a catalogued quote to be registered on the live factory with creation enabled before it is selectable.

LaunchHook: market enforcement

Each pool receives a frozen configuration when it is created. The hook then enforces the launch market throughout its lifetime.

Responsibility	Behavior
Pool gate	Accepts initialization only for a factory-registered launch
Liquidity seed	Creates the token-only position and verifies that no paired asset is required
Permanent lock	Rejects every removal and every external liquidity addition
Anti-snipe	Calculates the timestamp-based opening surcharge in the paired asset
Fee accounting	Splits the base fee between creator, platform, and valid referrer
Trade record	Publishes the callback executor, referrer, fee currency, fee amount, and optional comment in the Trade event; direction and trader attribution come from the complete receipt

During the opening anti-snipe period, LaunchHook keeps o1’s input-amount buy and sell flow open while applying the temporary surcharge. It rejects exact-output requests while the surcharge window is active. New Arc launches configure the opening total equal to the normal 1% base fee, so the surcharge is zero and the Hook treats the window as inactive. Existing pools retain their frozen settings; router support is separate.

The detailed callback and function surface is available in Functions and events.

Escrow, staking, and announcements

FeeEscrow tracks claimable balances in each pool’s paired asset. Anyone can trigger payment to the recorded recipient, while a recipient can also redirect their own claim. Only the launch hook can add new fee credits.

The staking contract is separate from token creation. Anyone can create an immutable reward vault for a compatible B20 or ERC-20 token and fund every epoch in advance. Participants deposit wallet-held tokens in independent lots, withdraw according to the vault’s fixed policy, and manually claim time-weighted rewards after each epoch. The owner may change the global fee for future vault creation but cannot change or cancel existing vaults, withdraw accounted assets, or pause participant actions. See the staking guide.

The announcement contract records each launch token. It resolves authorization through the active factory’s current creator rights, so accepted creator-rights changes also move announcement authority. The current creator can post announcements with a unique ID, description, and URI without receiving any token administration role.

Trust boundaries

• The factory owner can change defaults for launches that have not happened yet.
• The factory owner cannot change an existing token supply or remove liquidity. Creator-rights changes affect only current project authority and future creator-fee routing, without granting token or pool custody.
• The hook can credit fees only according to frozen pool configuration.
• The escrow can pay only swap fees already credited to it.
• The staking contract can move only principal and rewards according to each immutable vault and participant action.
• Transaction signing stays in the user’s wallet; o1 services never hold signing keys.

Monad deployment

Monad uses the ERC-20 minimal suite for standard crypto launches with MON, USDC and WETH. The adapter uses Monad’s no-deadline-argument SwapX overload while still enforcing the launch request deadline. It supports configured Uniswap/Pancake V3 and constrained hook-free external ERC-20 V4 pools; no Aerodrome factories are configured. The app searches bounded direct and USDC-bridge candidates. This is not a guarantee of the best route across all pools.

Arc deployment

Arc’s native USDC pays gas and the launch fee in 18-decimal units. The USDC pool quote uses the six-decimal ERC-20 interface over the same balance. cirBTC is a separate eight-decimal crypto quote in the application catalog. Pool trading fees and escrow claims use the selected quote currency. There is no separate wrapped-native token. This follows Arc’s USDC integration guidance.

ArcSwapXLaunchBuyAdapter accepts native or ERC-20 USDC funding. For native funding it converts the buy amount once by dividing by 1e12, then lets SwapX spend through ERC-20 approval with zero native value forwarded. Native buy amounts must be exactly representable with six decimals; otherwise the transaction reverts. It does not wrap USDC or exchange USDC for itself. With USDC as the registered quote, the route ends directly in the USDC/launch-token pool. For a registered cirBTC quote, the planner first acquires cirBTC through a configured V3 pool, then executes the final cirBTC/launch-token swap. It compares the 0.01%, 0.05%, 0.3% and 1% V3 fee candidates by output. Token-page trading supports direct paired-asset swaps and USDC settlement through the same acquisition planner in either direction. Missing liquidity or an output too small to quote prevents route preparation.

The attached adapter uses the deadline-enabled SwapX overload. It permits configured V3 pools and initialized, liquid, hook-free external V4 pools with static fees up to 5%; PancakeSwap and Aerodrome are not configured. The final launch pool must still use o1’s launch hook. Router pause and configuration checks, minimum output, complete input spending, balance preservation and allowance cleanup remain enforced. Accepted routes do not guarantee liquidity or the best quote.

The 5% value is a ceiling per external pool, not a fee automatically charged or a cap on all fees along a route. A permitted 0.3% pool charges 0.3%; quoting must account for each leg’s actual fees. The launch pool’s own Hook fee is separate. See Direct integration for funding amounts and approval targets.

See Arc configuration for current launch settings.

BSC deployment

BSC uses the same immutable ERC-20 launch suite for BNB, USDC and registered bStocks. Native BNB is the zero-address quote and WBNB is a separate wrapper. BSC USDC and all configured bStocks use 18 decimals.

BscSwapXLaunchBuyAdapter inherits the standard funding, authorization, exact-final-pool, minimum-output, deadline, residual-balance and allowance-cleanup checks. Clients supply the standard eight-field route; this BSC-only adapter encodes the router’s ten-field descriptors, with the reserved poolManager and parameters fields zero. The route limit remains four hops.

Acquisition searches configured Uniswap V3 and PancakeSwap V3 pools, including USDC/USDT bridge candidates, before the exact launch V4 pool. Pancake V3 candidates use 0.01%, 0.05%, 0.25% and 1% fees. Eligible external V4 descriptors can pass adapter validation, but the current acquisition planner does not discover every external V4 pool. The external-pool fee cap is 5%, not an added fee. Pancake V2, Infinity CL/Bin and Aerodrome are not part of this controlled route integration.

The adapter preserves unexpected balances and rejects incomplete spending or output below the protected minimum. Simulate the selected route before signing, as with other chain integrations.

X Layer deployment

X Layer uses the same immutable ERC-20 minimal suite, with native OKB, USDC, xETH and 45 wrapped stocks as supported quotes. The launch fee is 0.02 OKB, and pool fees and claims use the selected quote currency. Native OKB has 18 decimals and uses the zero address; WOKB is its separate wrapper and pricing identity.

The attached generic SwapXLaunchBuyAdapter uses the standard eight-field deadline interface. Native-funded atomic Dev Buy takes OKB directly into an OKB-paired launch pool, or acquires the selected ERC-20 quote through a supported route before buying the launch token. Token-page trading uses the X Layer SwapX proxy and its exact launch-pool route; sells approve that proxy. Compatible V3 acquisition is a separate path for registered ERC-20 quotes. The binding permits at most four hops and a 1% external-pool fee cap; external V4, V2, Infinity and custom external hooks are not enabled by this integration.

See X Layer contracts and configuration.