Pre-graduation trades must call the LONGSHOT router; ordinary aggregators need a direct integration. After graduation, the canonical V4 pool is available to V4 routers and aggregators.

The token is a normal ERC-20, not a redeemable share of the position and not a leveraged ETF. The keeper automates fee sweeps, isolated-position funding and holder-reward distributions. Position capital can be liquidated.

Metrics marked all-time come from the complete indexed history. When that history is unavailable, the site says “indexing” instead of substituting a rolling window or an estimate.

The site does not substitute sample launches or invented metrics. Failed or unsupported reads show an unavailable or empty state. Position PnL and open notional read directly from Hyperliquid's public API per pool; volume and fees routed read directly from each pool's own on-chain Swap/FeesCollected logs — none of that needs a separate backend. Only keeper execution history (a log of what the keeper did and when) has no on-chain or public-API source and stays unavailable until one exists.

A creator picks three things, locked for the token's life: the underlying asset, the direction, and the leverage multiple. Example — RobinGold, long BTC 5×.

The token's price is independent and market-driven — it is not redeemable for, or pegged to, the position. Position performance reaches the token only through buybacks.

Trading is live in that same transaction — no bonding curve, no separate pre-launch venue, no delayed graduation event. Costs gas only; the first real buyer's WETH is what enters the pool. Every launch starts at the same protocol-wide tick, so a creator cannot misrepresent a starting valuation.

A buy fees in WETH, a sell fees in the token — V3 always takes its fee from the input side. Both are tracked as their own complete 40 / 40 / 20 bucket set, so nothing is mixed or misattributed.

USDG → USDC is the only valid Across route between these two chains, confirmed live against their available-routes API. V3 fee accrual is silent, so the keeper polls every known pool rather than waiting on an event.

The position opens once accrued fee capital crosses the threshold. Each later crossing adds size to the same isolated position: read mark price and current equity, then add exactly enough size that leverage snaps back to the creator's target at that price.

⚠ Above 10× the liquidation buffer drops under ~10% of entry price — a routine move on the underlying can wipe the position's margin. Liquidated capital is simply lost; the airdrop pool is a separate stream and is unaffected.

Uniswap V3 pools are permissionless forever once deployed — nothing, including us, can stop trading on one. A deliberate tradeoff for a more reliable fee-capture mechanism, not an oversight.

Buybacks are funded by realized profit only — never mark-to-market — so a later reversal cannot claw back a buyback that already happened. A take-profit event partially closes the position and those proceeds fund the buy; a full close is never required.

The keeper implements reduce-only take-profit milestones with deterministic order IDs. Routing realized proceeds back into an automatic token buyback remains unwired.

The airdrop share accrues per token and is distributed to holders on a keeper-driven collectAndBuy → distribute cycle — pro-rata at snapshot, no claim step, no pull model. It is a separate stream from position capital: a liquidation does not touch it.

At $25 of pending value, launched-token rewards use a persisted holder snapshot and resumable transfer batches. Stock-reward pools remain unswept until a verified tokenized-stock venue is wired.

The keeper is rotatable and read live from the factory, so rotating the key never requires touching an already-deployed pool. It places real leveraged orders with live margin behind it — the recommendation is a scoped Hyperliquid agent wallet that can trade but cannot withdraw.

Launch parameters live on the pool as public immutables. collectFees() is permissionless — it only ever realizes fees the position already earned; the three sweeps are keeper-only. The Foundry suite runs against a real V3 factory, pool and WETH.

Each launch trades in a standard, unmodified Uniswap V3 pool — no hook, no curve. Anything that already reads a V3 pool works here unchanged.

bool isReal   = factory.isLaunchPool(pool);      // the authority
uint256 total = factory.allPoolsCount();
LaunchInfo[] page = lens.getLaunchesPaginated(0, 50);

event Launched(address indexed pool, address indexed token,
               address indexed creator, string symbol, address v3Pool);

One event, one transaction — no separate graduation event to watch. The address you verify is the LaunchPool, not the V3 pool: the pool itself carries no owner-specific marker.

raw = (sqrtPriceX96 / 2^96)^2        // token1 per token0
tokenIsToken0 ? WETH per token = raw : WETH per token = 1 / raw

address pool = factory.poolForToken(token);   // 0x0 if not ours

V3 sorts pools by raw address, so a launched token lands on either side of WETH. The asset symbol is a right-padded bytes32 — trim trailing zero bytes to decode.

Launch, buy, fee collection and sweep are all confirmed on real transactions. The Across bridge route is verified live; a real bridge deposit/fill and the Hyperliquid funding leg haven't been exercised yet — no pool has held a funded position.