For launchpads

Fund liquidity agreements from your launches

Your bonding-curve config (Meteora DBC) sends each token's unsold supply to your Mandate router, and at graduation it moves into an agreement's escrow as quoting inventory instead of into anyone's wallet. That covers the asks. A working agreement also needs quote tokens for bids, a fee budget, and a maker who accepts and posts a bond, so start with the tokens whose teams will fund those.

Set up your launchpad

Creates your router (once) and a DBC config whose leftover_receiver is the router. Graduated liquidity is permanently locked, and tokens migrate to DAMM v2 with a 0.25% fee.

Quote token mintTotal supply per tokenReserved for the market maker%Starting market capGraduation market cap

Connect a signing wallet (top right) to fund it.

Launch a token

Mandated configToken nameSymbol

At graduation

When the curve completes, anyone can run DBC's migration and withdraw_leftover. Then create the token's SLA with its DAMM v2 pool, register the launch, and anyone can route the leftover into the SLA's escrow. The repository's scripts/demo.ts runs this whole sequence end to end.

Draft the token's SLA See the live demo launch

What changes for your launches

Without oneUnsold supply goes to a wallet. Graduated pools sit nearly empty, and holders can't trade without moving the price.

With an agreementUnsold supply sits in escrow that can only quote. Once the team adds quote tokens and a fee budget and a maker accepts, both sides of the book are under a bonded commitment with a public status page.