LP plan

Turn a chosen pool and capital budget into an unsigned, simulation-backed plan.

Inputs

Require chain, wallet address, protocol version, exact pool identity, capital and max spend per token, objective, horizon, loss constraints, intended maintenance cadence, and approval preference. If the pool has not passed due diligence, stop and route to lp-research.

Workflow

1. Rebind chain ID, current block, wallet, pool, token order, decimals, fee, tick spacing or invariant, hook, manager, router, gauge, and reward assets from current reads.
2. Choose the position model from protocol planning. Do not apply concentrated-liquidity math to a full-range pair.
3. Design the range with range design. Use node scripts/range.mjs --help for deterministic tick snapping. Treat its output as arithmetic, not a strategy recommendation.
4. Compute the required token ratio at the quoted execution price with exact integer math or the current official SDK. Include wallet balances and loose assets from prior actions.
5. Quote the complete sequence. Apply max input, min output, minimum liquidity, price-impact, gas, deadline, and spend-cap constraints to every step.
6. Plan approvals with approval policy. Bind each approval to the exact token, spender, amount, mechanism, expiry, and cleanup rule.
7. Simulate every transaction from the actual wallet with the exact value and calldata. For sequential plans, later calldata that depends on mined output remains deferred.
8. Emit the plan contract. Include state reads and recovery checkpoints, but no signature request.