How it works

Liqio is five contracts of its own plus Uniswap v4. The factory launches coins and holds their liquidity, the hook charges the fee on every swap, the router lets the site trade any coin in HYPE, the token deployer creates the coin contracts and the oracle reads the pair's USD price from Hyperliquid at launch. Nothing in the set can mint, pause, tax or move anyone's coins.

The contracts

Contract	What it does
Factory	Launches a coin in one transaction: deploys it, creates its pool, seeds the whole supply as a single position and keeps that position. Records the creator, the pair, the starting cap and the pool id. Runs creator transfers and community takeovers. Has no function that removes liquidity, for anyone, and no owner after deployment.
Hook	Attached to every pool. On each swap it computes the fee (the flat fee, anti-snipe during the launch window), takes it in the paired asset, and credits the creator, the platform, the holder-rewards pot, the buyback pot and the trader's cashback and referral rewards. It enforces the max-wallet cap while its window runs and runs the buyback when the pot reaches its threshold. Anyone can trigger the payouts.
Router	Trades any coin in plain HYPE. For a stock- or USDC-paired coin it converts HYPE to the pair along a route through the pair's own pool before the pool swap, and back again on a sell. It names the trader and an optional referrer to the hook. It holds no funds between calls.
Token deployer	Creates the coin as a minimal-proxy clone (EIP-1167) of the coin implementation with CREATE2, at an address below the pair token's so the coin is always currency0 of its pool, initialises it and hands the whole supply to the factory. The clone keeps a launch near 1.2M gas, inside a HyperEVM small block.
Coin	An OpenZeppelin ERC-20 with EIP-2612 permits, initialised once in the launch transaction. No owner, no mint, no pause, no tax. Coins with holder rewards use a variant that adds pro-rata reward bookkeeping and a claim function.
Price oracle	Prices the paired asset in USD for the opening price, from HyperCore's oracle price precompile: HYPE from its perp market, a stock from its HIP-3 market, a stablecoin at a fixed price. Its list of pair tokens is set in its constructor at deployment and never changes. It is read only at launch and for display.
Uniswap v4 PoolManager	Uniswap's singleton on HyperEVM that holds every pool and executes swaps. Not a Liqio contract.

The launch transaction

A call to launch on the factory does the following, in order.

Price the pair

The factory asks the oracle for the USD price of the paired asset (WHYPE when HYPE is chosen) and reads the starting market cap preset the creator picked, say $3,000. From the two it computes the opening price of one coin in the paired asset: (cap / 1,000,000,000) / pair price.

Deploy the coin

The token deployer creates the coin as a CREATE2 clone of the coin implementation, searching salts until it finds an address below the pair token's, and initialises it in the same call: the whole supply of 1,000,000,000 coins is minted once, to the factory. If holder rewards are on, the rewards-enabled implementation is cloned instead.

Initialise the pool

A Uniswap v4 pool is created with the coin as currency0, the pair as currency1, a pool LP fee of 0, tick spacing 10 and the Liqio hook attached, at the opening price.

The hook records the coin, the pair, the creator address, the launch block and the fee settings (fee, anti-snipe, holder-rewards and buyback shares, max-wallet window). The hook re-checks the settings against its own caps, so a fee above 3% or an anti-snipe above 30% can never be registered.

Seed the liquidity

The factory places the whole supply (less a rounding reserve of 10¹² wei, one millionth of a coin) into one single-sided position from just above the opening price up to the highest tick. The position is recorded in the factory and held by it. Nobody can withdraw it: the factory has no function for that, and neither has the hook. Coins leave it when someone buys.

Dev buy (optional)

If HYPE was sent with the launch, the router converts it to the paired asset (no conversion for a HYPE pair) and the factory swaps it in the fresh pool. The coins go to the creator. This buy pays the normal flat fee, not the anti-snipe fee, and it is the only buy the pool accepts in the launch block. A stock with no HYPE route has no dev buy.

The opening price

Every coin opens at the USD market cap its creator picked from the factory's presets, whatever the pair. With a $3,000 preset and a supply of 1,000,000,000, the opening price is $0.000003 per coin. In pool terms that is converted into the paired asset: at an NVIDIA price of $180, one coin opens at about 0.0000000167 wNVDAx; at a HYPE price of $40, at 0.000000075 HYPE. The pool price is rounded down to the nearest tick, so the exact opening price is a little below the target.

The preset list is fixed at deployment: $3,000, $10,000 and $25,000. Each launch picks one by index, and nobody can change the list. The cap a coin opened at is recorded in capOf(token).

Every trade after that

A swap reaches the pool

From the Liqio site, from Uniswap, from an aggregator or from a contract: the hook does not care who sends the swap. Buying means paying the paired asset for coins; selling means paying coins for the paired asset.

The hook computes the fee

The flat fee the creator chose, plus the anti-snipe surcharge if the coin is inside its launch window and the swap is a buy. The fee is always measured in the paired asset.

The fee is taken

When the paired-asset amount is the one the trader specified (an exact-input buy or an exact-output sell) the hook takes the fee before the pool swap; otherwise it takes it from the paired-asset output after the swap. Either way the hook emits FeeTaken(token, fee, bps) and keeps the fee as a claim on the PoolManager.

The fee is credited

The holder-rewards and buyback shares, if any, go to the coin's pots. The rest is credited 60% to the creator and 40% to the platform; out of the platform's part, a cashback share is credited to the trader and a referral share to the trader's referrer, if they have one. Nothing is paid out yet; the amounts accrue per coin, and per user for cashback and referral.

Two more things can happen inside a swap. If the coin has a buyback and its pot has reached the threshold, the hook spends the pot buying the coin in its own pool and burns what it bought, in the same swap. If the coin has a max-wallet window and it is still running, a buy that would take one wallet's gross purchases over the cap reverts. Two rules apply to every swap. A sell is never blocked by the hook, in any block. And in the launch block itself the pool accepts no buy except the creator's dev buy, so nobody can land a buy in the same block as the launch.

Trading in HYPE

A stock-paired coin is priced in its stock, but the Liqio site always trades in HYPE. The router does the conversion: on a buy it wraps HYPE, swaps WHYPE to the stock on the stock's own pool (a PRJX 1% pool against WHYPE for wNVDAx, wSPYx, wGMEx and wSPCXx), then buys the coin in its Liqio pool; a sell walks the same path backwards and sends HYPE. A USDC-paired coin is reached the same way through the USDC/WHYPE pool. Buyers therefore never need to hold the pair token. A stock with no route yet (wMUx, wSKHYx, wQQQx) trades in the stock itself. Any wallet that holds the pair can trade with it directly through buyWithPair and sellForPair, or swap in the pool through any Uniswap v4 interface.

Claiming

Who	How	Paid in
Creator	`payCreator(token)` on the hook. Anyone can call it; the money always goes to the current creator. The creator can also call `claimCreatorFees(token)` on the factory, which counts as creator activity. The site has a claim button on the coin page and the profile.	the paired asset (HYPE for a HYPE pair)
Platform	`pushPlatform(tokens[])` on the hook, or `pushPlatformFees` on the factory. Anyone can call it; the money goes to the platform's fee recipient, an immutable address set at deployment.	the paired asset
Holders	`pushDividends(token)` on the hook moves the rewards pot to the coin (anyone can call it); each holder then calls `claimDividends()` on the coin. The site does both from the coin page and the profile.	the paired asset (HYPE for a HYPE pair)
Traders and referrers	`claimRewards(pairs[])` on the hook pays the caller's cashback and referral rewards in each pair asset. The site's Rewards page does it.	the paired asset (HYPE for a HYPE pair)
Buyback	Nothing to claim: the pot is spent in the pool and the coins are burned, by the swap that tips the pot over its threshold or by anyone calling `buybackBurn(token)`.	coins, burned

What never changes

The supply: 1,000,000,000 coins, minted once, with no mint function.
The pool: one Uniswap v4 pool per coin, with the hook attached and the liquidity position held by the factory.
The fee, the anti-snipe settings, the holder-rewards and buyback shares and the max-wallet window: recorded in the hook at launch, with no function to edit them.
Who receives the creator share: only the creator's own two-step transfer, or a community takeover after 30 idle days, moves the role; nothing else can.
The coin's own metadata (name, symbol, description, links, logo), which is stored in the token contract. The creator can set a different display metadata on the factory; nobody else can, and the coin itself is never changed.
The wiring: the factory's router, fee recipient and cap presets, the hook's factory and router, the token deployer's factory and the oracle's pair list are all set at deployment, with no owner left to change them.

Overview

Create

Trading

Security

The contracts

The launch transaction

The opening price

Every trade after that

Trading in HYPE

Claiming

What never changes

​The contracts

​The launch transaction

​The opening price

​Every trade after that

​Trading in HYPE

​Claiming

​What never changes

The contracts

The launch transaction

The opening price

Every trade after that

Trading in HYPE

Claiming

What never changes