unisafe LP insight

Every position of a manager, or one position by salt: when it opened, its pool, its lifetime fees and its events. Answered from the index, falling back to the Envelop history API and then to a log scan; the answer says which one served it and how current that source is.

What things are worth on a chain: token USD prices (the Uniswap gateway's map; the native token, address zero, priced as the chain's WETH), the gas price, and the typical USD cost of each operator operation at it (recenter, move, allocate, reinvest, claim). For weighing whether an operation pays before simulating it — a simulation's own gas estimate is better once there is one. `tokens` narrows the map and lists the ones it cannot price; `derived` names known stablecoins the gateway left unpriced, priced from a stablecoin they are pooled with; `stale` marks a copy served while a refresh fails; `gatewayStale: true` means the gateway's last answer (`gatewayDataAt`) is over 3 hours old, so the prices are that old answer's, not current.

Every unisafe LP manager (Stable and Volatile) the wallet currently owns, on every chain the Envelop oracle indexes, with the app link for each — the way in when you know the owner and not the managers. Other Envelop wNFTs the wallet holds are left out. An empty list means it owns none; when the oracle cannot answer this is an error, not an empty list.

Addresses currently authorised to rebalance a manager's positions. They can never withdraw — that is enforced by the contract. On the scan path the answer may be `partial`, which means a revoked operator could still be listed; from the index it never is.

Fee APR over the last 24 hours for each pool this manager is configured with, best first — the Uniswap gateway's figure, or the subgraph's last complete day for a pool the gateway does not list (`aprSource`). Only the manager's own pools are candidates: a move can target a pool only if the owner fixed it into the set when the manager was created. Pools that could not be scored are listed separately with the reason — a pool missing from the ranking is not a bad pool.

Compares the position's current pool against the rest of the manager's set and, when the gap is worth it, returns the numbers for a move: destination pool, ticks, and how much liquidity. A pool sharing no currency with the position is suggested only when the manager (v2.2) can bridge to it through another of its own pools; the answer then names that bridge. It returns NUMBERS, never calldata — pass them to the local envelop-mcp-lp server's propose_move, which re-derives each one against chain state and puts it through the policy and the price-oracle guard before anything is signed. The full ranking and the caveats come back with every answer so the suggestion can be disagreed with.