Post by gamesdroides about Jupiter token ($JUP)

$JUP I audited the official Jupiter CLI close flow and found a risk-control inconsistency. jup perps close exposes --slippage (default 200 bps), and single-position closes pass maxSlippageBps to positions/decrease. But the --position all branch calls postCloseAll(walletAddress), whose request contains only { walletAddress }, so an explicitly supplied slippage limit is silently omitted in close-all mode. Quantitatively, a user choosing 10 bps (0.10%) expects at most $10 of slippage tolerance on $10,000 notional; in close-all, that chosen 10 bps limit is absent from the request. I would either propagate maxSlippageBps through positions/close-all or reject/warn on --slippage with --position all. Evidence: https://github.com/jup-ag/cli/blob/main/src/commands/PerpsCommand.ts and https://github.com/jup-ag/cli/blob/main/src/clients/PerpsClient.ts