L
Base Sepolia · live deployment

Launch a token anyone can verify

Every badge below is recomputed from chain state in your browser: bytecode hashes against a published manifest, the LP lock ratio, the canonical-pair gate, and the exact fee terms. Nothing here is a promise you have to take on faith.

Create a launchBrowse launchesInspect the factory
Bonding curve…
Price rises linearly from the floor to the cap, then graduates to Uniswap V2.
Linear
price = a + 2·b·n/d
Deterministic
no oracle, no admin knob
Graduation
LP minted to the lock
Deployment integrity
…
runtime keccak256 vs published manifest
Revenue tier
—
license fee only
Curve trading fee
—
no post-graduation AMM fee is captured
Graduated liquidity
Permanently locked
minted straight to an immutable lock

This deployment

indexing factory events…
Contracts
LaunchFactory0x0195…5214
CreatorRegistry0x6a67…c918
OperatorTimelock0x0a32…2273
Quote assetWETH
ChainBase Sepolia · 84532
Creation fee—
Operator—
Kit recipient—
Verification checklistfull manifest →reading…
Deployment integrity
Correct chain
chainId 84532 matches the deployed configuration
Open explorer

What this does not prove: matching bytecode proves the deployed code is the published code. It does not prove the code is free of bugs, and no third-party audit has been completed yet — this page will say so when one exists.

Verify it yourself

Every claim above is reproducible from public chain data — no vendor attestation required. Concretely, on Basescan:

  1. 1Open the factory's Code tab and compare its runtime bytecode hash to the published manifest this page reads.
  2. 2On a graduated launch's pair page, check balanceOf(lock) against totalSupply() — that ratio is the LP-locked badge.
  3. 3Read the token's canonicalPair() and confirm transfers to it revert before graduation — that is the one-way gate.

Launches

indexed from factory events — no server, no database