For Projects (Launchers)

This section covers how to launch a token on Gavel, the required configuration, and what changes between Fair Launch and Curated Presale.

1) Choose a launch mode

Fair Launch (permissionless)

Best for most early-stage teams.

  • Anyone can create

  • Open participation

  • Uses safe defaults

  • Minimal “human trust” required

Curated Presale (curated)

For teams that want a more controlled launch.

  • Launch reviewed/approved

  • Optional allowlist

  • Optional private bidding

  • Optional per-wallet caps (if enabled)

Both modes use the same CCA engine — the difference is access + optional controls.


2) What you need before creating a launch

Token requirements

You’ll need:

  • Token name + symbol

  • Token contract address (ERC-20 on Base)

  • Decimals

  • Total supply

  • Creator / admin wallet (who configures the launch)

Supply for sale

Decide:

  • Sale size: how many tokens will be sold in the auction

  • Where sale tokens come from (typically transferred/escrowed into the auction contract)

Rule of thumb: don’t sell “too little” — thin sale supply often creates thin post-launch liquidity.


3) Required auction parameters (the core config)

Timing

  • Start time

  • Duration

Pricing

  • Floor price (minimum acceptable price / guardrail)

  • (Optional) other guardrails depending on launch type

Raise asset (pick one)

  • ETH or USDC or USDT One auction uses one raise asset.

Supply release schedule

How tokens are released over time during the auction. Examples:

  • Linear emission (steady release)

  • Tranches (stepwise release windows)

Your choice determines:

  • how much supply is available per block/window

  • how quickly price can move under demand

Unsold token handling (pick one)

  • Burn

  • Return to team

  • Send to treasury

Make this explicit in the listing — it changes incentives and buyer expectations.


4) Optional curated controls (Presale mode)

If you’re running a curated presale, you can enable:

Allowlist

  • Restrict participation to eligible addresses

  • Useful for community-first launches or compliance constraints

Private bidding

  • Hide bid details publicly during the auction (launch-dependent)

  • Useful when you want participation without broadcasting individual limits

Per-wallet caps (if enabled)

  • Limit max contribution per address

  • Reduces concentration and helps distribution


5) What happens at settlement (end of auction)

When the auction ends:

  1. Allocations finalize (who gets what)

  2. Participants claim tokens (and refunds if applicable)

  3. Liquidity is seeded on Uniswap v4 at the discovered price

    • depending on the launch, this happens via Gavel or Clanker routing

This is the main difference vs typical presales: proceeds don’t just “raise funds” — they form liquidity at launch.


6) Launch checklist (high-signal)

Before going live, make sure:

  • token contract is verified (source + decimals + supply)

  • sale size and emission schedule match your distribution plan

  • floor price is sane (not so high nobody fills; not so low it misprices)

  • unsold handling is clearly stated

  • curated launches: allowlist/private rules are tested with real addresses

  • you’ve prepared post-launch comms (what bidders should expect, claim timing, etc.)


  • 90% of teams should start with a Fair Launch unless they have a strong reason not to.

  • Use curated presale when you need:

    • controlled access (allowlist)

    • private bidding

    • extra launch support or stronger guardrails

Last updated