Launch path
The creator signs one factory transaction. It creates and distributes the token, opens the Uniswap v4 pool, and places the remaining 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.
Contract responsibilities
Factory: launch coordination
createLaunch coordinates the complete launch. The selected chain and paired asset determine the available factory. Base currently uses its crypto factory to create native B20 tokens. Robinhood uses its crypto or stock factory to create fixed-supply ERC-20 tokens. Every available route follows the same distribution and market-opening process.
The factory owner may update paired assets, supply, opening prices, liquidity ranges, fees, the platform fee receiver, and announcement support for future launches. The stock factories also support bounded quote batches, per-quote revisions, a restricted opening-price updater, and a switch for new stock-paired creation. Those changes cannot rewrite a completed token or pool.
Stock quote controls
Stock-paired factories keep their quote registry separate from crypto-paired factories.
Robinhood currently has 96 published stock quotes. No Base stock catalog is published yet. Deployment alone does not expose a route: the platform also requires catalogued quotes to be registered on the live factory with creation enabled.
LaunchHook: market enforcement
Each pool receives a frozen configuration when it is created. The hook then enforces the launch market throughout its lifetime.
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 until the total fee reaches the normal 1% rate.
The detailed callback and function surface is available in Functions and events.
Escrow, vesting, 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.
VestingVault shows each schedule and the amount available now. Anyone can trigger a claim, but payment always goes to the recorded beneficiary. Only the factory can create a schedule, and no administrator can change or recover it later.
AnnouncementRegistry records the creator at launch. That creator can later 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 pool or token.
- The hook can credit fees only according to frozen pool configuration.
- The escrow can pay only swap fees already credited to it.
- The vesting vault can send tokens only to the recorded beneficiary.
- Transaction signing stays in the user’s wallet; o1 services never hold signing keys.