THROTTLE
beforeSwap
First-block cap
For the first N blocks after the pool opens, per-wallet size is capped. Snipers can still buy — they just cannot buy the whole book. The overflow fee goes to the pool, not to a bot.
→ cap(wallet, n_blocks)
Live on Robinhood ChainHooks · Liquidity pools · Uniswap v4
Uniswap v4
liquidity pools
on Pons
UNILIQUID turns a token launched on Pons into a real Uniswap v4 liquidity pool governed by hooks — dynamic fees, snipe throttles, floors enforced in code. No bonding curve. No migration cliff.
v4
Uniswap singleton
06
Hook modules
00
Migration events
100%
Fees routed on-chain
LIQUIDITY POOLSHOOKSUNISWAP V4PONSCONCENTRATED RANGESDYNAMIC FEESSINGLE-SIDEDNON-CUSTODIALLIQUIDITY POOLSHOOKSUNISWAP V4PONSCONCENTRATED RANGESDYNAMIC FEESSINGLE-SIDEDNON-CUSTODIALLIQUIDITY POOLSHOOKSUNISWAP V4PONSCONCENTRATED RANGESDYNAMIC FEESSINGLE-SIDEDNON-CUSTODIALLIQUIDITY POOLSHOOKSUNISWAP V4PONSCONCENTRATED RANGESDYNAMIC FEESSINGLE-SIDEDNON-CUSTODIAL
01The problem
Four ways a pool loses liquidity
None of these are market problems. They are missing rules — and until Uniswap v4, a pool had no way to hold any.
L1
The migration cliff
The curve fills, liquidity is dumped into a raw pool, and the first block belongs to whoever pays the most gas. The crowd that funded the launch buys the top of a candle it created.
L2
One fee for every weather
A static fee charges the same at 3am on a dead chart as it does mid-40% candle. LPs get paid least exactly when they carry the most risk.
L3
Floors made of promises
"Liquidity locked" usually means a multisig and a screenshot. Nothing in the pool stops the exit. Liquidity leaves precisely when it is needed.
L4
Ranges that stop earning
Full-range liquidity earns dust. Concentrated liquidity earns well until price walks out of the range, then earns nothing at all — silently, for weeks.
| Capability | Bonding curve | Raw v3 pool | Standard launchpad | Uniliquid |
|---|---|---|---|---|
| Real Uniswap pool at launch | — | ✦ | — | ✦ |
| Rules enforced on every swap | — | — | — | ✦ |
| Fee reacts to volatility | — | — | — | ✦ |
| Exit blocked by code, not trust | — | — | — | ✦ |
| Single-sided deposit | ✦ | — | ✦ | ✦ |
| No migration event | — | ✦ | — | ✦ |
Comparison describes categories of design, not named products. Uniliquid contracts are unaudited — see risk.
02Three moves
Launch. Seed. Govern.
01
Launch on Pons
Fixed supply, a form, a wallet signature. No Solidity, no Foundry, no deploy script. Pons handles creation — that part already works.
pons.create({
supply: fixed,
creator: 0x…
})
02
Seed a Uniswap v4 pool
Uniliquid opens a canonical v4 pool at the address your hook set was mined for, and seeds it single-sided. No counterpart token required, no bootstrapping ritual.
poolManager.initialize(
key: {…, hooks: 0x…8aC0},
sqrtPriceX96
)
03
Govern every swap
The hook runs inside the swap, not beside it. Fees adapt, snipes throttle, exits stay shut until the unlock block. Rules cannot be skipped, because the pool will not execute without them.
beforeSwap() → gate + price fee
afterSwap() → route buyback
beforeRemove()→ enforce lock
Non-custodial throughoutContracts hold liquidity. Never keys. Every transaction is signed in your wallet.
03Hooks
Six hooks inside the swap
A Uniswap v4 hook is not middleware sitting next to the pool — it is called by the PoolManager during execution. If the rule reverts, the swap does not happen. That is the entire reason this design is possible now and was not before.
FEE
beforeSwap
Dynamic fee
The fee is priced per swap against realized volatility. Calm markets stay cheap. Violent ones pay liquidity providers for the risk they are actually carrying.
→ fee = f(realized_vol)
SEED
beforeAddLiquidity
Single-sided liquidity
Deposit one token. The hook derives the range from current depth and places it. No counterpart, no manual tick math, no leftover dust.
→ range = auto(depth)
BUYBACK
afterSwap
Fee routing
A slice of every fee is routed into a standing bid below spot. Fees stop being a receipt and start being a floor that grows with volume.
→ route(fee_share) → bid
LOCK
beforeRemoveLiquidity
Enforced lock
Liquidity cannot leave before the unlock block. Not a multisig, not a pledge, not a screenshot — a revert. The pool refuses the transaction.
→ require(block > unlock)
GUARD
beforeSwap
TWAP guard
Swaps that shove price outside a band against the oracle in a single block are rejected. Cuts the sandwich, keeps the market.
→ reject(|Δp| > band)
Composability
Hooks are selected per launch and encoded in the hook contract address itself — v4 reads the permission bits straight out of the address, so a pool cannot quietly gain a capability it was not deployed with. What you mine is what you get, permanently.
hooks: 0x…8aC0 // THROTTLE · FEE · LOCK
// permission bits mined into the address
// immutable for the life of the pool
04Liquidity pools
Concentrated liquidity, held in range
Depth is a distribution, not a single number. Uniliquid shows that distribution and lets the hook hold the position inside it — so the range keeps earning instead of quietly going dark.
TOKEN / USDGv4 · dynamic fee
In range Idle depth
min
max
spot
−60%−30%price+30%+60%
Range width
±18%
Fee tier
dynamic
Position
single-sided
Lock
enforced
Chart is schematic and illustrates the mechanism. It is not live market data.
Concentrated
Liquidity sits in a tick range instead of spread from zero to infinity. Same capital, far more depth where the price actually trades.
Single-sided
Deposit one token. SEED derives the range from live depth and places the position for you.
Rebalanced
When price walks out of range, the position is re-centred in one flow instead of a withdraw-swap-redeposit sequence.
Verifiable
Pool address, hook address and every position are readable on the explorer. Nothing about the state lives on our server.
05Stack
Four layers
Uniliquid does not run its own AMM, its own chain, or its own launchpad. It writes the rules layer that was missing between them — and everything else stays canonical.
Launchpad
Pons
Fixed-supply token creation on Robinhood Chain. Form plus wallet signature — no Solidity required. Pons Labs operates the interface; keys and assets stay with the user.
AMM
Uniswap v4
Canonical PoolManager singleton. All pools live in one contract, which is what makes hook-gated execution and flash accounting cheap enough to run on every swap.
Rules
Uniliquid hooks
Six modules, selected per launch, with permissions mined into the hook address. Immutable once the pool is initialized.
Chain
Robinhood Chain
Arbitrum Orbit L2. Settlement in USDG. Blocks are cheap enough that per-swap rule execution is not a luxury.
Specification
- Custody
- Non-custodial
- Pool type
- Uniswap v4 singleton
- Hook permissions
- Address-encoded
- Upgradeability
- None, post-init
- Settlement
- USDG
- Verification
- Blockscout
Execution path
swap()
└ PoolManager.unlock()
└ hook.beforeSwap()
├ THROTTLE gate
├ FEE prices swap
└ GUARD band check
└ swap executes
└ hook.afterSwap()
└ BUYBACK routes fees
06$UNILIQUID
The token launches on Pons
No private round, no seed allocation, no separate contract standard. $UNILIQUID goes through the same launchpad and sits in the same kind of hook-governed Uniswap pool it is meant to make possible.
01
Hook activation
Turning on a hook module for a pool requires $UNILIQUID. Scarce rules, priced.
02
Fee discount
Protocol fees paid in $UNILIQUID settle at a discount, and the paid amount is burned.
03
Buyback route
BUYBACK routes a share of pool fees into a standing $UNILIQUID bid below spot.
04
Rule governance
Parameter bands for FEE and GUARD are set by $UNILIQUID vote, within hard-coded limits.
The loop
More pools open→
More swaps clear→
More fees accrue→
BUYBACK bids $UNILIQUID→
Rules get cheaper to run↺
The loop only turns if pools actually trade. There is no emission schedule propping it up and no staking yield paid out of thin air — if volume stops, the loop stops. That is the honest version.
07Roadmap
Six phases
Dates are intent, not commitment. Anything on this list can slip, and a hook that is not ready does not ship early.
P1Weeks 1–3
Testnet pools
THROTTLE, FEE and SEED live on testnet against a canonical v4 PoolManager.
shipping
P2Weeks 4–6
LOCK & GUARD
Lock enforcement and TWAP banding, plus the hook address miner.
next
P3Week 8
Mainnet beta
Capped TVL for the first 90 days. Pons integration in the launch flow.
next
P4Month 3
BUYBACK
Fee routing into the standing bid. $UNILIQUID launches on Pons.
planned
P5Month 5
Rebalance engine
One-flow re-centring for out-of-range positions.
planned
P6Month 6
Open hook registry
Third-party hook modules, reviewed and bonded.
planned
Open a pool
with rules
Liquidity pools, hooks and Uniswap v4 — wired into a Pons launch from the first block.
LP-ing can lose money
Read this partContracts are unaudited
Uniliquid hooks are new code running inside live swaps. An audit is scheduled, not finished. TVL is capped for the first 90 days for exactly this reason.
LPing can lose money
Providing liquidity is not yield. A concentrated range converts your position into the losing side of a trend. Hooks change the rules of the pool, not the direction of the market.
Rules cut both ways
THROTTLE caps you as well as the sniper. GUARD can reject your swap. LOCK means you cannot exit early either — that is the point, and it applies to everyone.
Young pools are thin
A launch pool has little depth by definition. Slippage on early swaps can be severe regardless of how well the hooks behave.
Pons listing is not endorsement
Any token can launch on Pons, and a Uniliquid pool does not vet the token inside it. Rules govern the liquidity, not the honesty of the team.
Figures on this page are schematic
Charts and numbers shown here illustrate mechanisms. They are not live market data and not a projection of returns.
Nothing on this page is investment advice, an offer, or a solicitation. Uniliquid is software. You sign every transaction yourself and you keep your own keys — which also means no one can reverse a transaction for you.