Launch factories
Base, Robinhood, BSC and X Layer each use one current launch factory for both crypto-paired and stock-paired creation. The current and historical addresses are linked from Production contracts, and the complete topology is available inlaunch-contract-suites.json. Event consumers must retain historical factories and use the ABI matching each suite’s contractVersion.
Active production factories
The current Base, Robinhood, Monad, Arc, BSC and X Layer factories do not expose the older
feeDefaults() aggregate read. Read the named fee getters and enumerate feeComponents(0..feeComponentCount-1). They also replace the older quotes() tuple with quoteConfig(), use one global nativeLaunchFee() for every quote, and use bandTemplate() instead of bands().
The current fee component rows on all six chains are CREATOR at 50 bps, PLATFORM at 30 bps, and REFERRER at 20 bps. Their sum is the 100 bps base fee. Component bps are direct shares of the trade amount, not percentages that need to be applied to baseFeeBps again.
Chain-specific token deployment
Base creates and validates native B20 tokens. Robinhood, Monad, Arc, BSC and X Layer call their dedicatedLaunchTokenDeployer to create immutable ERC-20 tokens. Robinhood, Monad, Arc, BSC and X Layer integrations can read launchTokenBytecodeHash(LaunchParams) and TOKEN_ADDRESS_SUFFIX to prepare a deterministic token address ending in 01 before signing.
Launch events
All current minimal factories additionally emit
PriceUpdaterUpdated and LaunchCreationEnabledUpdated. Historical factories retain their original event names; use the ABI for the exact contract that produced the event.
LaunchHook
The hook exposespoolConfig(poolId) and poolFeeComponents(poolId) for each launch pool. These reads return the pool’s frozen fee and anti-snipe configuration plus its current creator and creator fee recipient. The factory registers and seeds a pool; ordinary trading then occurs through Uniswap v4.
Trade.executor is the router or callback sender and is not guaranteed to be the trader’s wallet. Indexers should derive direction and trader attribution from the complete transaction receipt, including the matching Uniswap swap and router execution context.
FeeEscrow
Events:
Credited and Claimed.
Earlier launch contracts use their original claim function names. Resolve the fee contract recorded for the launch before encoding a claim.
AnnouncementRegistry
Events:
TokenRegistered and AnnouncementPosted.
Earlier launch contracts retain their original creatorOf, usedId, post, CreatorRegistered, and Announcement surface.
Robinhood, Monad, Arc, BSC and X Layer launch tokens
Robinhood, Monad, Arc, BSC and X Layer tokens expose standard ERC-20 reads and transfers. When profile editing was enabled at launch, the metadata authority can callupdateName, updateSymbol, updateContractURI, and updateExtraMetadata. No mint, burn, pause, owner, upgrade, or recovery function exists.
Current Robinhood/BSC crypto-paired and stock-paired tokens and Monad/Arc/X Layer crypto-paired tokens use the same LaunchToken implementation, are created through their chain-specific current factory, and must end in 01.
Staking contract
One staking contract serves every vault on its chain. The vault creator and complete immutable configuration determine thevaultId.
Use the verified explorer ABI for exact types and encoding. See the staking guide for the reward, withdrawal, and claim rules.
