Parameters Reference (Launch Configuration)
This section lists the key parameters a project sets when creating a Gavel launch, what each parameter means, and what it affects.
A) Token info
Token name / symbol Displayed across the UI.
Token address (Base) The ERC-20 contract being sold.
Decimals Used to compute exact allocations.
Total supply For transparency (not always equal to sale size).
Creator / admin wallet The address that creates and manages the launch configuration (launch-dependent permissions).
B) Sale sizing
Sale size (tokens for sale) How many tokens are distributed through the auction. Affects: distribution breadth, volatility, and liquidity depth.
Sale % (optional UI) Sale size expressed as % of total supply (informational).
C) Timing
Start time When bidding begins.
Duration How long the auction runs.
Pre-bidding (optional UX) Some launches may allow users to prepare bids before live start (implementation-dependent). If enabled, bids only begin filling once the auction is live.
D) Pricing
Floor price A minimum price guardrail. The auction will not clear below this price. Affects: minimum valuation and who is willing to bid.
Max price (user-defined per bid) Not set by the project, but important to understand: bidders fill only when clearing ≤ their max.
E) Raise asset (pick one)
Choose one:
ETH
USDC
USDT
Affects: who can participate, funding friction, and perceived volatility.
F) Supply release schedule
Defines how sale supply becomes available over time.
Common patterns: Linear release A steady emission rate across the duration.
Tranches Supply released in steps/windows (e.g., more supply later, or multiple phases).
Affects:
per-block supply
how clearing prices evolve
how much early bidders can fill
G) Unsold token policy (pick one)
What happens to tokens that are not sold by the end of the auction:
Burn Reduces circulating supply. Signals scarcity.
Return to team Keeps supply with the project (must be communicated clearly).
Send to treasury Moves to a public/DAO treasury (aligns with community funding narratives).
Affects: incentives and post-launch supply expectations.
H) Curated controls (optional, presale mode)
Allowlist Only allow approved addresses to bid.
Per-wallet cap (if enabled) Limit max contribution per address.
Private bidding Bid details are not publicly visible during the auction (launch-dependent). Affects: privacy and coordination dynamics.
I) Settlement & liquidity parameters
Liquidity venue Uniswap v4 (Base).
Liquidity routing Liquidity seeding may occur via Gavel or Clanker depending on launch configuration.
Liquidity seeding rule Proceeds are used to seed liquidity at the discovered auction price so trading can start immediately.
J) Recommended defaults (simple)
If you want the “standard” Gavel feel:
Use Fair Launch unless you need allowlist/private bidding
Keep the schedule simple (linear release)
Pick a raise asset your community already holds
Be explicit about unsold token policy
Last updated