How launches work

Gelvx fair-launch architecture: CREATE2 token, Uniswap V3 1% pool, forever-locked LP.

Every Gelvx launch is a single atomic transaction through ZoracleLaunchFactory. There is no bonding curve and no migration step — liquidity is live in a Uni V3 pool immediately and the position NFT is held by ZoracleLocker permanently.

Launch flow

Creator calls factory.launch() with metadata URIs and optional dev buy.
CREATE2 deploys ZoracleToken (immutable ERC-20, no mint/tax/blacklist).
Factory creates WETH/token pool at fee tier 10000 (1%).
Full supply is added as single-sided liquidity; position NFT sent to locker.
Launched event emitted with token, pool, deployer, positionId, launchId.

Token identification

Vanity: address ends with hex suffix 20a (brand z0r).
factory.isLaunchedToken(token) returns true.
ZoracleToken(token).factory() equals 0x76c1139ca3E2A7633081532cBf8cf5E80bAeddfe.
IPFS metadata includes launchpad: "Gelvx" and launchpadUrl.

Trading

Swaps route through the token's Uni V3 pool (WETH pair, 1% fee). ZoracleZap supports one-tx ETH → token buys for factory-launched tokens only. Any router (Maestro, Rick, Gelvx UI) can trade the same pool.

Fresh launches

DEX aggregators may lag new pools. Gelvx enriches token pages from on-chain launch data when GeckoTerminal / DexScreener have not indexed yet.