Every launched token is one fixed, leveraged directional bet on a major asset — funded by the token's own trading fees, run as a single isolated perp on Hyperliquid.
A launchpad on Robinhood Chain where each launched token is a fixed, leveraged directional bet on a major asset, funded by the token's own trading fees. Not a memecoin creator-fee model, and not a tokenized derivative.
The site does not substitute sample launches or invented metrics. Failed or unsupported reads show an unavailable or empty state. Keeper execution, position PnL, and distribution history still require a public keeper/indexer API.
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.
Where the protocol is undecided or unbuilt, it says so here rather than around it.
A normal ERC20 that trades in its own Uniswap V3 pool against WETH. Its price is independent and market-driven — it is not redeemable for, or pegged to, the leveraged position. The position is a side vehicle funded by the token's own trading fees; it reaches the token price only through buybacks.
No. There is no NAV, no redemption and no rebalancing against a basket. That is deliberate: it keeps the product in the same mechanical shape as a fee-mechanic token rather than a tokenized derivative.
Every trade pays a fee that splits 40 / 40 / 20 — position capital, holder airdrop pool, operating costs. A buy fees in WETH, a sell fees in the token, and each currency keeps its own complete bucket set.
Once accrued position capital crosses the threshold ($50.00 by default). Until then the token trades normally with no position behind it. Every later crossing tops the same isolated position back up to the creator’s target leverage.
No. Underlying, direction and leverage are immutable for the life of the token — including after a liquidation event, where the position reopens with the same parameters.
That capital is lost. The token keeps trading, fees keep accruing, and the position reopens on the next threshold crossing with the original parameters. The airdrop pool is a separate stream and is untouched by a liquidation.
⚠ Above 10× the liquidation buffer drops under ~10% of entry price — a routine move on the underlying can wipe the position’s margin. Leverage is capped per asset by the factory owner, and the cap is curated by hand against Hyperliquid’s real listings.
At $25 of live pending value, the keeper snapshots holders, buys the selected reward, and pushes pro-rata transfers in resumable batches; there is no claim step. Stock rewards remain unswept until a verified stock-buy venue is wired.
A rotatable role read live from LaunchFactory. It can sweep accrued fees out of any pool and move position-capital, airdrop and ops funds onward. It cannot change a launch’s parameters, and for Hyperliquid it should be a scoped agent wallet that can trade but not withdraw.
No — including us. Uniswap V3 pools are permissionless forever once deployed, and there is no pause or emergency-stop role anywhere in the protocol. That was traded off deliberately for a more reliable fee-capture mechanism.
No. The pool seed is deposited single-sided and permanently locked; no remove-liquidity path exists anywhere in the contract.
There is no bonding curve or migration — trading starts in the launch transaction itself. Graduation is reached at 4.2 WETH of paired principal in the permanently locked V3 position. It is a status milestone only; trading continues in the same pool.
Any Hyperliquid perp. The asset is an open bytes32 symbol, not a fixed enum — the gate is the factory owner setting a leverage cap for that symbol before a creator can launch against it.
Yes — live on Robinhood Chain mainnet (chain id 4663). Launch, buy, fee collection, and sweep are all confirmed on real transactions with real ETH.
Those values are not exposed by the configured public sources. Keeper order state, position PnL, and distribution history need indexed events or a public keeper service, so LONGSHOT leaves them blank instead of estimating them.
No. Image, website, X, Telegram and GitHub are launch metadata for display only. LaunchFactory.launch() does not write them.
Watch LaunchFactory’s Launched event, verify with isLaunchPool(), and read display data from LaunchLens.getLaunch(). The Docs page has the discovery calls, the lens fields and the price formula.
Nothing here is financial advice. Leveraged positions can be liquidated in full. This is a live mainnet deployment — every transaction uses real ETH.