Contract reference
The baselaunch contract reference lists every launcher contract on Base with every function and event, who may call each function, and the contract's addresses.
Every launcher contract has its own page here with every public and external function and every event: 269 functions and 87 events across 14 contracts. The custom errors an integrator is likely to hit are explained in the docs, under errors. The pages are generated from the compiled launcher 2.1.0 sources, so signatures, selectors and event topics are exact. Descriptions come from the contracts' own NatSpec where they have it.
The badge under each function says who can call it, read from its modifiers and caller checks. "Anyone" means the contract does not restrict the caller; a call can still revert on its own conditions. Every row has its own link, for example launchToken on the factory.
- BaseLaunchFactory
Creates every coin and its bonding curve, keeps each launch's record and frozen fee terms, and graduates a finished curve into its locked Uniswap v4 pool.
63 functions, 25 events
- BaseLaunchRouter
The one entry point for a launch: creates the coin through the factory and lands the creator's opening buy in the same transaction, optionally in holders mode, with a launch interface and a trade referrer.
5 functions, 1 events
- BaseLaunchInterfaceRegistry
Records, per coin, the launch interface (front end or integrator) entitled to the interface share of that coin's creator-side fees. No owner; only the current interface can hand its entry on.
6 functions, 1 events
- BaseLaunchBondingCurve
One per coin. Sells the coin against the pair asset on a constant-product curve with a virtual reserve, charges every fee in the pair asset, and hands its reserves to the factory at graduation.
48 functions, 14 events
- BaseLaunchToken
One per coin. A fixed-supply, burnable ERC-20 with the coin's logo, description and socials; the whole supply is minted to its bonding curve. It grants nobody any power over the coin.
18 functions, 2 events
- BaseLaunchHook
The single Uniswap v4 hook on every graduated pool: takes the trading fee and creator fee after each swap, pays any referrer, converts and sweeps pool fees, and holds the fee policy new launches snapshot.
48 functions, 19 events
- BaseLaunchFeeEscrow
The pull-payment record of every fee in a launcher set: curves, the hook and the buyback vault credit recipients here, and each recipient claims its own balance. No owner, no rescue path.
10 functions, 2 events
- BaseLaunchBuybackVault
Holds every coin's bought-back supply and releases it linearly over five years, splitting each release between the creator recipient and the protocol on the coin's frozen protocol share.
19 functions, 7 events
- BaseLaunchLocker
Holds every graduated pool's full-range position NFT and the coins left over at graduation, forever. It has no withdraw, transfer or arbitrary-call function.
14 functions, 5 events
- BaseLaunchDeployer
Deploys each coin and its bonding curve with CREATE2 for the factory, so their addresses can be computed before the launch is sent.
3 functions, 0 events
- BaseLaunchGraduationExecutor
Mints each graduated pool's full-range position to the locker for the factory, then sends rounding dust to the protocol fee recipient (dust of the coin itself goes to the locker).
6 functions, 2 events
- BaseLaunchGraduationGuard
A stateless check the factory created in its own constructor: it replays the Uniswap v4 mint rules so a curve can only graduate into a pool seed v4 will accept.
2 functions, 0 events
- BaseLaunchHoldersDistributorFactory
Creates one holders distributor per holders-mode launch as a clone of a single implementation whose code cannot change, and holds the publisher key every distributor trusts to post reward epochs.
11 functions, 4 events
- BaseLaunchHoldersDistributor
One per holders-mode coin (a clone of the implementation): the coin's creator fee recipient, set at launch, which pays those fees to holders through published Merkle epochs, each claimable for 90 days. The creator cannot move it; the protocol owner can redirect it after a 3-day notice.
16 functions, 5 events
Addresses are listed for launcher 2.1.0, where new coins launch, and for launcher 2.0, which keeps serving the coins launched before the cutover. A coin stays on the set that launched it. The functions and events are the 2.1.0 contracts'; the 2.0 contracts are an earlier version of the same code and have no interface registry, so check a 2.0 contract's verified source on Basescan before relying on a detail listed here.