Launchpad integration overview

Integration reference for the CheesePad launchpad. It covers the flows a third-party integrator works against: pools and microsales and Melt Pools (three ways to run a token sale) and vaults (where a tax token's revenue goes, and how to build your own).

If you are indexing sales, building a launch UI, wiring up a trading bot, or shipping a custom revenue vault, start here.

What's in here

Doc	Read it when you want to
getting-started.md	Connect to the launchpad, pick a network, understand fees and roles
pools.md	Run a presale, fair launch, or subscription with a token you already have
microsale.md	Create a microsale, contribute, finalize, claim, refund, and read sale state
melt-pool.md	Launch a token that trades on a price curve and graduates to a DEX
vaults.md	Route a tax token's revenue into a vault, and use the two vaults CheesePad ships
custom-vault.md	Build and deploy your own vault + factory
events-and-data.md	Index events, do reverse lookups, and read every struct/enum/constant

Three ways to launch

CheesePad has three launch styles. They are separate flows with separate functions.

• Pools are for a token you already have. You bring the token contract and the parameters (price, caps, whitelist, vesting), and the launchpad runs the sale and lists it. Pools come in three shapes: Presale (fixed price), Fair Launch (price set by how much is raised), and Subscription (oversubscribe, then allocate). See pools.md.
• Microsales mint the token for you from a platform template. Less to configure, one token per sale, a fixed price, an optional buy/sell tax and revenue vault. See microsale.md.
• Melt Pools mint the token and sell it on a continuous price curve. People buy and sell at any time, the price moves with demand, and the pool graduates to a DEX once it sells out. See melt-pool.md. ("Bonding curve" is the technical term for the same thing, and the spelling used throughout the contract ABI.)

Microsale and Melt Pool tax tokens can route their revenue into programmable payout logic, which is the vault path in vaults.md.

The model

You talk to CheesePad through a single contract, the launchpad. Point one contract instance at the launchpad address for your chain and call into it for every operation.

Pools and microsales run a timed raise: contributions collect in a per-sale fund manager until the sale fills, then finalize adds liquidity on a Uniswap V2 style router and locks or burns the LP. A Melt Pool skips the window: it lists the token against a price curve immediately, and graduates to a DEX when the curve sells out. For a pool you bring your own token; for a microsale or a Melt Pool the launchpad mints one. If a minted token charges a buy/sell tax, that tax is routed to a fee receiver, which can be a plain wallet or a vault you attach at launch.

                  bring your own token / minted
   creator ───────────────────────────────▶ launchpad ◀─────── contributors / traders
                                                │
                     pool ──────── timed raise, you supply the token
                     microsale ─── timed raise, launchpad mints the token
                     melt pool ──── continuous price curve, launchpad mints the token
                                                │
                        tax on trades           │
   trader ──swap──▶ tax token ──▶ settles tax ──routes revenue──▶ fee receiver
                                                                   (wallet or vault)

Key addresses

The launchpad address is your single entry point per chain. There is no separate address for pools, microsales, or Melt Pools — all three run on this one contract.

Network	Chain ID	Launchpad
BNB Chain (mainnet)	56	0xD9CcE715619fA9082d21375B6B37A3a0d99138F4
BNB Chain (testnet)	97	0x0AA21d47b600B04527c09BbD9A30aF32cb64f6cF
Robinhood Chain	4663	0x7E0752B42f9db92F12E221E10fFfa10bfE8668C6

Vault factory addresses (for vault-backed launches) are in vaults.md.

A few things worth knowing up front

• One address, one ABI. You call the launchpad address with the Launchpad ABI (see getting-started.md). Every function in these docs lives on that one contract.
• The fundManager address is the handle for a sale. Almost every call and lifecycle event, for pools, microsales, and Melt Pools alike, is keyed by it rather than by the token or an index. Reverse lookups by token (and by vault, for microsales) exist too.
• Amounts are raw integers. Token amounts use 18 decimals. Native (BNB) amounts use 18 decimals. ERC20 quote amounts use that token's decimals.
• Time is Unix seconds, taken from the block, not your clock.