Contracts

Deployed on Base mainnet, chain ID 8453.

The source is not verified on Basescan yet. Until it is, you cannot read the code of what you are sending funds to, and none of the claims on these pages are independently checkable. That is a real gap, not a formality.

External contracts it uses

Calls worth knowing

Before launching

// Non-reverting. Returns whether it would be allowed, and why not if not.
registry.status(address quote)
  returns (bool eligible, Decision decision, Report report)

// The bar this particular asset has to clear — $15,000 if listed, $50,000 if not.
registry.requiredDepthUsdE8(address quote) returns (uint256)

Launching

launchpad.launch(LaunchConfig cfg) payable returns (address token, bytes32 poolId)
launchpad.predictToken(address creator, bytes32 salt) returns (address)
launchpad.launchFee() returns (uint256)

LaunchConfig carries feeRoute (0 keeps the fees, 1 buys back and burns) and feeRecipient (zero means the launching wallet), so both choices are made in the launch transaction rather than as a follow-up.

After launching

// Anyone can call. Proceeds only ever reach the recorded recipient, the sink and the treasury.
feeVault.collect(address token)

// Creator only. Both take effect from the next collect.
feeVault.setFeeRoute(address token, FeeRoute route)
feeVault.setFeeRecipient(address token, address recipient)

// Reads
feeVault.launchOf(address token) returns (Launch)   // includes the PoolKey
feeVault.feeRouteOf(address token) returns (FeeRoute)
feeVault.feeRecipientOf(address token) returns (address)
feeVault.owed(address token, address who) returns (uint256)   // a payout that could not be pushed
feeVault.claim(address token)                                  // collect one

Owner powers

The owner can retune the depth bars, the fee bounds, the treasury, the buyback sink, the curated list and the gates. It cannot touch a launch's liquidity, change an existing launch's creator share, or redirect a creator's fees.

Ownership transfer is two-step everywhere: a handover that is never accepted leaves the current owner in place rather than sending the protocol to a wrong address.

Today the owner is a single EOA. It should be a multisig behind a timelock, and the contracts do not enforce that themselves.