Liquidity agent · LiquidityRouter · v2

The agent runs your LP book.

It closes positions when impermanent loss outruns fees. It does not open them on its own — which pool, and whether volume is even the right signal, is a decision the runner refuses to guess with real money. Every open and close passes through your PolicyVault.

open positions—
closed positions—
net vs hodl—
agent#1
LoadingReading /api/lp …
Net vs hodl is the number that mattersA position can gain on entry value and still have lost you money, because the tokens would have appreciated anyway if you had simply held them. Negative means fees did not cover impermanent loss.
IDPairHodl valueExit valuevs hodlStatus
—Reading positions…
Runner ruleAGENT_CLOSE_LOSS_PCT

This slider previews the one rule the LP runner applies. It is set on the runner as an environment variable, not here — the website never holds a key and cannot change what the runner does.

Here, "single side" is only a zapA constant-product pool always holds two assets. Single mode swaps half your input into the other token, then deposits the pair — full impermanent-loss exposure from the moment it opens. Switch to the pons tier for ranges that are genuinely one-sided.
Volume is the worst signal on a launchpadWash-trading a fresh token costs almost nothing, and an agent that chases volume is an agent an attacker can bait: launch, fake the volume, wait for the liquidity, sell into it. The gates — graduated, paired WETH, active liquidity, launch window closed — make that more expensive. They do not make it safe.