Fair-launch token auction platform built on Balancer's Liquidity Bootstrapping Pools (LBPs). Projects deploy a weighted-pool with a decaying weight schedule (e.g. 95/5 → 50/50 over 72h) so price falls over time absent demand, achieving fair price discovery without a presale. Maintained by the Alchemist (alchemistcoin) team.
- 01no-presale fair-launch token sales
- 02Balancer LBP deployment and orchestration
- 03decaying-weight price-discovery auctions
- 04treasury-side raises with anti-whale dynamics
- 05EVM (Ethereum, Polygon) launches via Balancer v2
- pnpm add @balancer-labs/sdk @balancer-labs/sor viem
| Variable | Scope | Description |
|---|---|---|
| EVM_RPC_URL | Server | Ethereum or Polygon mainnet RPC for reading LBP weights, swapping, and tracking the auction. |
| COPPER_LBP_POOL_ID | Client | Balancer pool ID (bytes32) of the specific Copper LBP you are interacting with — published per-auction on copperlaunch.com. |
CopperLaunch does not ship a first-party SDK; its LBPs are vanilla Balancer v2 LiquidityBootstrappingPool contracts and you interact with them via `@balancer-labs/sdk` (or directly via the Balancer Vault). To buy into an active LBP, fetch pool weights with `vault.getPoolTokens(poolId)` and compute the current price from the weighted-pool formula `spotPrice = (balanceIn / weightIn) / (balanceOut / weightOut)`. Submit swaps through `vault.swap({ kind: SwapKind.GivenIn, poolId, assetIn, assetOut, amount, ... })` with explicit `limit` and `deadline`. Read the public `weights[]` and `endTime` from the LBP contract to confirm you are inside the auction window before swapping.
- ⚑LBP weight schedules can be manipulated by the project owner (the pool owner can update weights or pause swaps) — always read the pool owner's permissions and the actual `_endWeights` / `_startTime` / `_endTime` on-chain, do not trust the auction page UI.
- ⚑Decaying-weight curve means buyers near the start pay a price premium that decays over time; quote `spotPrice` immediately before submitting and use a tight `limit` to avoid front-runs.
- ⚑Copper itself is a UI; the canonical contracts are Balancer's — verify the LBP factory address matches Balancer's deployments before approving spend, otherwise you may be approving a malicious clone.
- ⚑Many LBP projects attempt to recover unsold tokens at the end; if your wallet bought near the floor, monitor the `withdraw` window because LP shares burn at auction close.
- ⚑Jurisdictional restrictions and KYC are not enforced by the LBP contract itself — projects sometimes geofence the Copper UI but the underlying Balancer pool stays open to anyone.
- ⚑Cross-chain post-listing: LBP tokens are typically deployed on a single chain; bridging via LayerZero/Wormhole post-graduation requires a wrapper contract that may not exist at launch.
- ⚑Rug risk: projects can revoke pool admin privileges (or not) and can pre-fund a wallet to dump at TGE — surface tokenomics + admin-key status before letting users buy.