Claiming, reducing, closing
Three actions, what each one produces, and the difference between removing everything and closing.
The three actions
| Action | What happens | Position token |
|---|---|---|
| Claim fees | Uncollected fees are sent to your wallet. Liquidity untouched. | Kept |
| Reduce | Part of the liquidity is withdrawn along with any fees. | Kept |
| Close | All liquidity withdrawn, all fees collected, token destroyed. | Burned |
Removing 100% and closing are deliberately separate. Removing everything empties the position and leaves the token in your wallet, so it can be refilled later. Closing destroys it, and that cannot be undone.
Order of operations
Closing is a single transaction carrying the withdrawal, the collection and the burn together in that order. The burn refuses while any liquidity or any uncollected fee remains, so the order is not stylistic.
A position that has already been emptied is a special case: there is no liquidity to withdraw, so the standard sequence reverts. That path adapts to collect and burn without a withdrawal, which is what stops fees becoming permanently stranded inside a position nobody can finish closing.
Simulation and slippage
Every write is simulated first, and a failed simulation never opens your wallet. The amounts shown in the confirmation come from that simulation rather than from a separate calculation, so the screen and the transaction cannot drift apart.
Withdrawals carry a minimum-amount guard derived from the simulated result, and every transaction carries a deadline. Both were tested by making them deliberately impossible and confirming the transaction refuses rather than proceeding quietly.
Fees in wrapped ether are collected as the wrapped token and left for you to unwrap. Automating that adds edge cases to a path that handles money, for a convenience worth a few seconds.