Indexer & bot integration

Gelvx-launched tokens are fully onchain-verifiable. Do not rely on Gelvx Discover alone — index the factory directly.

Recommended flow

1. Index factory.Launched logs from block 11_482_559
2. Store: token, pool, deployer, positionId, launchId
3. Verify: factory.isLaunchedToken(token) == true
4. Trade: Uni V3 pool at token.pool(), fee tier 10000 (1%), vs WETH
5. Optional badge: address ends …20a OR read logoURI from token

Verify a token is Gelvx-launched

// Primary check
bool gelvx = IZoracleLaunchFactory(0x76c1139ca3E2A7633081532cBf8cf5E80bAeddfe).isLaunchedToken(token);

// Secondary
address tokenFactory = IZoracleToken(token).factory();
bool matches = tokenFactory == 0x76c1139ca3E2A7633081532cBf8cf5E80bAeddfe;

// Vanity (brand z0r → …20a)
bool vanity = (uint160(token) & 0xFFF) == 0x20a;

Enrich metadata

• On-chain: name(), symbol(), logoURI(), twitter(), pool(), creator()
• IPFS tokenURI JSON: launchpad, launchpadUrl, image, description
• Gelvx token API fallback: GET /api/hood/token/{address}?chain=hood

What Gelvx does not require

• Partners do not need to route through Gelvx UI to trade launch pools
• Track A KOL skim only applies to Gelvx-routed swaps (optional integration)
• No API key required for on-chain indexing