Cetus protocol pool fee claims and wallet receipt checks

Choose fee collection when the position should stay open

Use the fee-collection action when your intended outcome is to receive accrued earnings while keeping the existing position. Removing liquidity serves a different purpose: it takes deposited assets out of that position. Closing it goes further and ends the position. A transaction that combines those operations needs a different review from a fee-only claim.

Cetus CLMM accumulates trading fees separately from the liquidity that providers deposit. This separation makes collection possible without reducing the position. Leaving earnings unclaimed also does not add them to its liquidity. Reinvestment requires an additional liquidity operation, with the token requirements that apply to that position.

Match the claim to the position you control

Position identity and token amounts

The claim must target the position that earned the fees, with its matching pool and token types. A token-pair label alone does not establish that match. Record the position identifier, accrued amounts, liquidity amount, and price range before proceeding.

Cetus identifies the pool and position separately in its collection operation. These identifiers distinguish the claim even when several positions involve the same assets. Token quantities provide a clearer comparison than a combined currency valuation, which also responds to market prices.

Authority and transaction contents

The signing account must have the authority required to use the position. A wallet connection establishes which account the interface is showing; it does not establish that every displayed position belongs to that account. A missing or inaccessible position needs an ownership check before any claim attempt.

Review the proposed operations and recipient alongside the network fee. For this task, the transaction should collect earnings and deliver them to your intended wallet. Unexpected liquidity removal, position closure, or token conversion changes the requested outcome.

Collect the fees or decline an unexpected withdrawal

Consider a directly held position with claimable fees and a requirement to keep its liquidity unchanged. Apply this short checklist before authorizing the proposed transaction:

Open full-size image

• Match the connected account to the position that holds the accrued fees.
• Match the position identifier, pool, and token types to your starting record.
• Confirm that the proposal collects fees without removing liquidity or closing the position.
• Check the intended recipient and the displayed network fee.
• Proceed only when the proposed effects fit that fee-only outcome.

A matching fee-only proposal

Approve the matching transaction, then inspect its execution status and token receipts. Compare the position's liquidity amount and range with your starting record. A successful receipt at the intended address, alongside unchanged liquidity and range, completes the claim. Stop there if your purpose was to move earnings into the wallet.

A proposal that also removes liquidity

Decline a proposal that includes withdrawal when the position must remain intact. Use the same comparison: account, position, recipient, and liquidity effect. Rejecting the unsigned proposal leaves that proposed withdrawal unexecuted. Inspect the refreshed position before preparing a fee-only action; do not approve the withdrawal merely because it also collects earnings.

Which tokens arrive when you claim pool fees?

A fee claim collects the pool tokens that the position has accrued, with amounts determined by trading activity and its eligible liquidity share.

Swap direction affects the composition of those earnings because the pool charges trading fees in each swap's input token. The accrued amounts therefore need not have equal quantities or equal values. Collection does not automatically convert them into a preferred asset. Any conversion adds a swap, with its own execution conditions and costs.

What does a fee claim cost?

A fee claim requires a blockchain transaction, so the proposed network charge belongs in the decision about whether to collect now. Use the estimate for the actual transaction rather than assuming a fixed collection cost. Simulation can estimate gas and expose proposed effects before signing.

The fee that the pool charges traders and the network charge for collecting earnings serve different purposes. The former contributes to accrued trading revenue; the latter pays for transaction execution. Compare the value of the fees you would receive with the collection transaction's network charge using a consistent valuation basis. A successful collection does not by itself establish a profitable liquidity position.

Open full-size image

Why can the fee display differ after a successful claim?

The fee display can differ because the interface reads delayed data or because further eligible swaps generate earnings after collection. A displayed balance is a snapshot.

The transaction record provides the execution status and balance changes for affected addresses and token types. It can distinguish a completed receipt from an interface refresh problem. A transaction identifier alone does not establish success: an executed transaction can still report failure. If the outcome remains unresolved, inspect that transaction before submitting another claim.

Indexed reads can trail execution, so a wallet or position view may update afterward. Compare token quantities once the view reflects the transaction. If the received asset also pays the network fee, account for that charge when interpreting its net balance change.

The existing range still governs future fee earnings

Cetus CLMM distributes swap fees to liquidity that is in range when the swap occurs. Collecting past earnings does not move the range or restore an inactive position to participation. The claim changes where accrued tokens sit, while the existing liquidity remains exposed to pool activity and price movement. Adjusting liquidity is a separate decision from receiving accrued fees.

Open full-size image