Wallet not connected
The hook fee recipient and the LP position NFT owner follow the address connected at launch (the connected address) — not a fixed address. Name, ticker, and fee are read from the Customize Token panel in the Launch Console below when a button is pressed. The launch sequence (Path A, passed a full 6/6-stage simulation): deploy token → deploy hook → approve → approve → open pool. Estimated total gas ±0.002 HYPE.
We are family — but we can rug each other.
One console for the whole family on Elysium: launch a token, open its pool, and manage it in the open. The family's rules are printed below — including the uncomfortable one.
Family first
Everyone launches under one roof: one console, one shared hook pattern, one pool standard — Rugs (RUGS), 1,000,000,000 supply.
Rugs stay in the family
Liquidity on this console is withdrawable by design, and every token page says so. If the LP gets pulled, it was family — check the LP mode before you buy.
No secrets
Fees, LP mode, and pool status are printed on the page for everyone to read. What you see is exactly what the contracts do.
Family-Only Console
Access to this console requires holding at least 1,000,000 RUGS in your connected wallet on Elysium. Connect your wallet — your RUGS balance is read from chain with balanceOf and the console unlocks automatically if you qualify.
Paste the contract address of a token you launched — from this session or an earlier one. The console verifies on chain that the connected wallet is the token's creator, its LP position owner, or its hook fee recipient; only then does the token appear in My Tokens & Pools below with pool info and working Claim Fees / Withdraw LP buttons. If the connected wallet is not the creator, the token is not added and no controls are shown. Loaded tokens are re-verified from chain on every wallet connection, exactly like the saved launches.
Price
—
Appears once the pool is live
Market Cap
—
Calculated from the pool price
Total Supply
1,000,000,000 RUGS
100% goes into the pool at launch
Holders / Transfers
— / —
Token not created yet
Connect your wallet to see your launches — this list only shows tokens created by the connected wallet (creator / hook fee recipient / LP position owner). Tokens from other wallets are not shown here. A launched token missing from this list can be loaded with the “Load a Token by Contract Address” box at the top of this page.
The sniper watches the Uniswap V4 PoolManager for newly opened native HYPE / token pools and buys with the connected wallet through a small helper contract that talks to the PoolManager directly — the same direct V4 path as the rest of this console. No private key or seed is ever asked for or stored: every buy is a transaction your wallet signs. Purchases go through only after the honeypot shield below passes.
Every newly opened HYPE-paired V4 pool on Elysium is a target: when one appears, the sniper runs the safety checks and buys it (once per pool).
If this token already has a live HYPE pool, it is processed as soon as you start. If not, the sniper watches and buys the moment its pool opens.
The quick buttons fill the amount — or type your own. This is the exact HYPE spent per buy and the maximum per buy (plus network gas). It is never exceeded.
Confirm: when a target is detected and passes the checks, an in-page preview shows the exact token, the exact HYPE amount and the expected tokens — nothing is sent until you tap Buy on that preview. Your wallet still confirms the transaction itself.
Status: idle.
Sniper log
Paste the contract address of an ERC-20 token that is already deployed on Elysium. The console verifies the contract from chain — contract code, name, symbol, decimals, total supply, and the token balance in the connected wallet — then the token can be launched from here: if it has no pool yet, continue with Approve → Open Pool in the steps below (Deploy Token is skipped, and the shared hook already used by VEGITO & GALANT is reused when available); if it already has a pool, the token joins the My Tokens & Pools list and can be managed, claim fees, and withdraw LP like any other token.
Choose the contract type for a new token created with the Deploy Token button in step 1. Every type follows the same flow: Deploy Token → Deploy Hook → Approve → Open Pool, and its type is shown in the My Tokens & Pools list. The “New Token — reset console” button returns this choice to Standard Token.
The standard contract proven in previous launches: 1 billion supply, 18 decimals, no owner, no tax / burn / rebase.
Taken when tokens leave the pool (the buyer receives the rest).
Taken when tokens enter the pool (the seller sends, the pool receives the rest).
Tax is taken from transfers that touch the pool and sent to this address in the same transaction. Ordinary wallet-to-wallet transfers are not taxed; the launching wallet is tax-free so pool seeding stays whole. Maximum 20% per side.
Every transfer burns this percent of its amount: the recipient receives the rest, and total supply decreases permanently. Transfers from the launching wallet are burn-free so 100% of supply enters the pool whole at launch. Maximum 10%.
Positive = supply grows, negative = supply shrinks. Every balance changes proportionally.
Rebase runs automatically: the first transfer after the period elapses triggers it; it can also be called manually through the rebase() function in the contract.
1 · Deploy the token contract
Create an ERC-20 token with the name & ticker from the Customize Token panel. Supply 1 billion, 18 decimals, all of it to the connected wallet first. For a token loaded from a contract address, this step is skipped — the token already exists.
2 · Deploy the fee hook contract
A Uniswap V4 hook that takes the fee (set in the Customize Token panel) from every swap, accumulated as a claim in the PoolManager for the fee recipient = the connected address. The hook address is searched automatically (CREATE2 salt) so its hook flags are valid.
3 · Approve token to Permit2
Approve the ERC-20 for exactly the pool supply (1 billion tokens) to Permit2 — not unlimited.
4 · Approve Permit2 to POSM
Permission in Permit2 so the Position Manager (POSM) can pull tokens for the LP position. Exactly 1 billion, expires in 30 days.
5 · Open pool + add liquidity
POSM multicall: initializePool (HYPE pair, LP fee 0.01%, hook attached) + mint position — 100% of supply enters the pool single-sided, the creator holds 0 tokens. The LP position NFT is issued to the connected address.
6 · Claim hook fees
Once the pool is running and swaps happen: the fees accumulated in the hook (HYPE + token) are sent to the fee recipient recorded in the hook — the launching address. Can be called anytime, repeatedly.
7 · Withdraw liquidity (LP)
Runs in 2 steps: step 1 claims any claimable creator fee first (skipped automatically when the claimable fee is 0), then step 2 withdraws the LP — POSM decreaseLiquidity + take (and burn the position at 100%) for the position NFT owned by the connected address. Each step is its own wallet confirmation. The portion follows the slider in the Withdraw Liquidity card: 100%. Tokens + HYPE + accrued LP fees return to the connected address.
Console log
No transfers yet
On-chain transfer history will appear here after the token launches, like the Transfers tab on an explorer token page.
No holders yet
The only holder of the supply at launch is the Uniswap V4 pool (100%). The holder list fills in as soon as the first swap happens.
Default: Rugs — always re-check for duplicate RUGS tokens on Elysium before launching.
Uppercase letters, no spaces. Shown on the explorer as (TICKER) next to the name.
Default 1%. Taken by the hook on every swap (buys and sells) and sent straight to the creator wallet in the same transaction — separate from the 0.01% LP fee.
By default the LP position NFT stays in the creator wallet, is not burned, and does not go to a locker — so liquidity can be withdrawn partially or fully at any time. Locked mode disables that withdrawal.
Fee math illustration only — not a price or a promise of results. The hook fee is paid in HYPE on the swap side.
Withdrawal uses the LP position NFT in the wallet connected at launch (the position owner). The portion here is used by the Withdraw LP button in the Launch Console above; execution is a separate transaction after launch, from the position owner’s wallet.