Skip to main content
Every KEK.PRO launch token exposes its metadata and canonical pool. The factory adds launch-level state, and the locker exposes custody and fee routing.

Token metadata and launch record

Treat strings and URLs as untrusted creator input. Sanitize them before rendering.

Validate the canonical pool

Do not trust a pool address from a URL or indexer alone. Require:
  • launched.exists is true;
  • launched.token equals the requested token;
  • liquidityPool() equals launched.pool;
  • token getters match launched.deployer, pairedToken, and poolFee;
  • the pool’s token0 and token1 contain exactly the launch and quote tokens;
  • the pool’s fee equals launched.poolFee;
  • launched.isToken0 matches address ordering.
The launch record snapshots token-specific values. A later update to a factory launch or DEX configuration does not rewrite an existing token.

Read custody and fee policy

feeAllocation is global and owner-updateable. It applies when fees are collected. It is not snapshotted per token and does not switch automatically at TGE. The original deployer may update that token’s creator fee recipient. The current contracts do not implement an administrative community-takeover flow.

Read mutable configuration

Read launchFee, getLaunchConfig, getDexConfig, and locker or compounder policy immediately before constructing a write. Use the approved manifest to choose configuration IDs, then verify every returned dependency. Keep immutable launch facts separate from mutable global policy in your cache.
Last modified on July 29, 2026