Hub

Automation

A position needs maintenance: fees to claim, a wall that price left behind, an exit to take when it fills. Those are transactions you would otherwise have to send by hand, at the right moment, awake. A background worker can do each of them for you, but only the specific job you switched on, on the specific position you chose.

three jobs · you choose per position
Autoharvestclaims fees
Sweeps accrued fees once they are worth the gas.Hourly6hDaily$1$5$25
Trailing wallfollows price
Rebuilds a stranded wall closer to price, after it has been out of range for the dwell window.1h6h12h24h48h72h
Limit orderfills once
Withdraws the wall once price has traded through it and stayed there, then stops for good.5m15m1h6h
Each is opt-in on the position you pick, and each can be switched off there. A position can run autoharvest alongside one of the other two; trailing and limit are mutually exclusive, because one keeps a wall alive and the other retires it.

Autoharvest

Concentrated positions accrue trading fees continuously, but claiming them is a transaction. Autoharvest watches what a position has actually got waiting and sweeps it once it is worth more than the gas to go get it.

  • Threshold: the minimum claimable value before a sweep fires. Pick $1, $5, $25, or type your own. It exists so you never spend $3 of gas to claim $2 of fees.
  • Cadence: how often the worker checks (hourly, every 6 hours, or daily). Checking is free; only a sweep costs gas.
  • The number it measures is what the position will actually pay out, including farm and emission rewards the same claim sweeps, not a stale figure stored on the position. If a fee leg can't be priced, the run skips rather than guessing past your threshold.
  • On the EVM chains it also refuses to spend silly gas: a claim only goes through when the estimated gas is both under your ceiling and a small fraction of what's being claimed. An estimate it can't price is treated as too expensive, not as free.

It's offered wherever fees are separately claimable, which means the concentrated models on every chain. On constant-product pools there is nothing to enrol: fees compound into the reserves and you realise them when you remove.

Trailing walls and limit orders

Both watch the same event: price walking away from a single-sided wall. They answer it in opposite ways. A wall that is merely stranded can be moved. A wall that has been traded straight through has already done its job, and the only thing left is to take the fill.

chase it · or close it
Trailing wallPrice runs away from your wall. After the dwell window the wall is torn down and rebuilt just off the new price, so it can actually fill. Capped at a few moves a day so a steady drop can't walk it down.
position stays open
Limit orderPrice trades all the way through your wall, so the band is already swapped into the other asset. Once it stays through for the confirmation window, the position is withdrawn once and never re-provided.
position closes, once
Both watch the same event: price leaving your wall behind. Trailing keeps the position alive by moving it; a limit order takes the fill and gets out.

Trailing walls

A wall sits at a fixed price. A trailing wall follows the market: once it has been out of range for the whole dwell window, the worker tears it down and rebuilds it just off the current price, so it can actually fill instead of sitting somewhere the market has left.

Dwell
How long the wall must stay continuously out of range before it may move, from 1h up to 72h. The clock resets if price comes back, so a wick doesn't trigger a rebuild.
Offset
How far past the current price the rebuilt wall's near edge sits, in basis points. Tighter fills sooner; wider gives price more room to come back to you.
Moves per day
A hard cap on repositions in a rolling 24 hours, so a steady grind down can't walk your wall all the way with it.

It chases price to get filled

That is the whole trade-off, and it is worth reading twice. A trailing bid wall follows price down. If the market snaps back after it moves, you filled lower than if you had left the wall where it was. It is an exit aid for a wall you want filled, not a way to farm more fees.

Limit orders

Post a wall, arm a limit order, and when price trades all the way through it the worker withdraws the position once and never re-provides. That is the fill-and-stop behaviour single-bin LPs build by hand, done for you.

  • Confirmation window: how long price must stay past the wall before the withdrawal fires, from 5 minutes to 6 hours. The order has already filled by then; this only filters a wick that pokes through and comes straight back.
  • Which side you posted is fixed when you arm it. A filled ask and an untouched bid can look identical on-chain, so naming the side is what makes the fill test exact.
  • It won't arm on a wall that has already traded through (that one wants withdrawing, not arming), and it never re-arms after it fires.

A limit order in effect, not on a book

Worth being precise, because the name promises more than any AMM can deliver. There is no order sitting on a book. Your capital is live liquidity the whole time, and the price you get is what the band averaged as it filled, not a single limit price. What lp.xyz adds is the part you would otherwise have to sit and watch for: it notices the fill and gets you out.

What you hand over

Automation needs to sign without you there, so turning it on is a deliberate two-step: you accept the terms, then delegate signing. The delegation creates a scoped credential inside your own account, for one wallet address, and the server verifies it actually works before recording the grant, so a client can't fake it.

what you hand over
It can
  • Claim fees on the positions you enrolled
  • Rebuild a trailing wall closer to price
  • Withdraw a filled limit order, once
It cannot
  • Move funds out of your wallet
  • Touch a position you never enrolled
  • Keep signing after you revoke
Automation signs with a scoped credential created inside your own account, for one wallet address, and only to run the job you switched on. Revoking it takes effect immediately.
  • Every automated action lands in your activity feed with its signature, exactly like an action you took yourself.
  • If a run can't proceed safely it pauses that position and records why (delegation revoked, position closed, a build or signature that failed) instead of retrying blindly. Switching the job back on clears the pause.
  • Revoke at any time, and it stops signing immediately. Archiving a wallet also parks every job on it without losing your settings.

Maintenance, not protection

Automation keeps a position you chose to open in good working order. It does not watch the market for you and it will not save you from the market moving against that position. Every job here is off until you switch it on, per position, and off again the moment you say so.