Safety and troubleshooting

What Wave can and can't do with your funds

Wave holds your position NFTs so it can act on all of them at once. That's the only reason.

The only action that moves your positions is your own Close, and it sends everything to the wallet that built the wave.
There's no path that sends a wave's positions or proceeds anywhere else.
Wave never takes principal. Its fee is a share of collected trading fees, only when collected.
There's no upgrade mechanism. The contract that's deployed is the contract that runs.

Some tokens skim a percentage on every transfer. ARGUS takes 1% on the way out of its pool.
Wave measures what actually arrives and sizes positions to what it really holds.
You'll still see the token's own cut in what comes back. That's the token, not a Wave fee.
On v3, with many bins on such a token, the last bin can end up empty after the skim and the build fails without a clear reason. Try fewer bins.

Amount too small for this range — add more, use fewer bins, or narrow the range.
Insufficient balance — you hold less than the wave needs. The swap card can help.
Fix the range — check that min is below max.
Pool price is at the edge of tick space — a dead pool. Find the token's live pool.
This pool has no usable price — same thing, caught earlier.
Preview failed: … — the contract turned down the plan and says why. Persistent? Tell us the pool and what you entered.
This pool's hook controls liquidity — a v4 hook that can interfere with positions. Wave sits these out.
Price out of band — the price moved outside your slippage band before confirmation. Retry, or widen slippage in Advanced.
Slippage — the deposit would have come in under your minimum. Same fix.

Most often it's the price band on a fast-moving token. Retry or nudge slippage up.
Gas isn't usually it; Wave already buffers the estimate.
Failing repeatedly? Send the pool, range, bins, shape, amount, and the message you saw.