Skip to main content
These rules are code, not policy. They are checked by the factory at launch and by the hook on every swap, and there is no function anywhere in the set that relaxes them. The source of every contract is verified at deploy; see Contract addresses.

​
The coin

  • Supply is exactly 1,000,000,000 coins with 18 decimals, minted once when the clone is initialised in the launch transaction. There is no mint function.
  • The token has no owner, no pause, no blacklist, no transfer tax and no upgrade path: it is a minimal proxy whose implementation address is fixed in its bytecode, and the implementation itself can never be initialised. A transfer can only fail the standard balance and allowance checks.
  • Name, symbol and metadata are set at initialisation and never change.
  • Coins with holder rewards add bookkeeping and a claim function and nothing else; the bookkeeping never charges, blocks or slows a transfer.

​
The pool and its liquidity

  • One Uniswap v4 pool per coin: coin as currency0, pair as currency1, LP fee 0, tick spacing 10, the Liqio hook attached. The hook refuses to register any other key.
  • The whole supply is seeded as one single-sided position owned by the factory. It is liquidity that cannot be withdrawn, by anyone: the hook has no liquidity permissions at all, and the factory has no function that removes or collects the position. Coins leave the position when someone buys them.
  • Buying raises the price along the single-sided curve; selling lowers it. There is no other mechanism that moves the price.

​
The fee

The factory checks these bounds before it deploys anything, and the hook checks them again in registerPool, so no caller, the factory included, can register a pool outside them.

​
Trading

  • A sell is never reverted by the hook and never pays more than the flat fee (plus the priority-fee surcharge, which depends only on the sender's own tip).
  • In the launch block, the only buy the pool accepts is the creator's dev buy sent by the factory.
  • After the launch block, the only buy the hook reverts is one that would take a wallet over a running max-wallet cap.
  • The fee settings of a pool are read from the hook's storage, which is written once at registration. Nothing writes to it afterwards; only the creator address can change, through the factory's transfer or takeover.

​
No operator

There is no admin and no operator. No contract in the set has an owner after deployment. Nothing can be paused, hidden, blocked, overridden, re-pointed or withdrawn by anyone. The following are fixed at deployment, and no function changes them:
  • Launches cannot be paused. There is no pause or resume function.
  • There is no hidden flag and no pair block list. The contracts hold no listing flag at all.
  • Display metadata is the creator's alone: setCreatorMetadata is the only setter, and metadataOf(token) returns the creator's metadata if set, else the coin's own. There is no override.
  • Launch liquidity cannot be withdrawn by anyone. There is no collect function of any kind.
  • Anyone can launch, and only for themselves. There is no launcher allowlist and no launchFor.
  • The router is fixed at deployment.
  • The platform fee recipient is an immutable address set at deployment. pushPlatformFees stays, callable by anyone, and pays that address.
  • The starting market cap presets are fixed at deployment: $3,000, $10,000 and $25,000.
  • The cashback and referral shares are constants: 25% and 25% of the platform part.
  • On the hook, the reward split is constant, the factory and router addresses are wired once in the deployment sequence and then fixed, and setCreator can only be called by the factory, for a creator transfer or a takeover.
  • The oracle's list of pair tokens and their HyperCore markets is set in its constructor and can never be changed or extended.
  • The token deployer's factory address is wired once at deployment, then fixed.
The deployer performs this one-time wiring during the deployment sequence; its setup rights are then renounced, and owner() on the factory returns the zero address. Adding a new pair token means a new Liqio version with its own factory and oracle; coins on an older version keep trading there forever. The creator's own tools (fee claims, display metadata, the two-step transfer, the community takeover after 30 idle days) are unchanged. See Security model.
x
Liqio on HyperEVM