Four Checks When Liquidity Mining Rewards Stall

When liquidity mining rewards stall, trace the emissions contract, position accounting, rate calculation and claim path before changing your position. A dashboard can show zero estimated rewards even while a contract is accruing them, or display an annualized rate after emissions have ended. Start with the pool’s on-chain state and the transaction history for the wallet that supplied liquidity.

For a Base pool, first identify the contract that holds the position and the contract that distributes rewards; they may be separate. A guide to using BaseSwap on Base covers the venue and its swap flow. For a farm issue, the relevant evidence is the farm’s own rules, contract state and events, not the swap interface alone.

Have emissions actually stopped?

Check the reward contract’s configured emission rate and active period. Liquidity mining programs commonly distribute a fixed amount per block or per second, but the specific schedule depends on the program. An end timestamp, exhausted reward balance, changed rate or paused contract can each leave a position earning nothing. A frontend timer or APR label is a display; it does not prove that tokens are still being emitted.

Use a block explorer or the protocol’s published contract interface to inspect the relevant state and recent transactions. Look for administrative calls that changed the schedule, funding transactions that replenished the reward balance, and pause or resume events if the contract exposes them. Compare the current state with the pool’s documented schedule. A configured rate can still fail to produce payouts if the contract has no reward tokens available.

Also check whether the program distributes rewards continuously or updates them in epochs. In an epoch-based design, the next allocation may not take effect until a boundary or a separate update transaction. That can create a gap without indicating a broken contract. The distinction matters: waiting for the next scheduled update is different from expecting an ended schedule to restart by itself.

Does the contract count your position as eligible stake?

Rewards accrue only to stake the distribution contract recognizes. Providing liquidity to an automated market maker usually creates a receipt token or another representation of the pool share. If the farm requires that receipt to be deposited in a staking contract, holding it in the wallet is not enough. Check the wallet’s farm deposit and the contract’s recorded stake, rather than relying on the pool balance shown elsewhere in the interface.

Then inspect the program’s eligibility rules. Some programs reward a single pool share uniformly; others use gauges, boosted weights, lockups or minimum deposits. A withdrawal, transfer, expired lock or changed gauge allocation can alter eligible stake. If rewards accrue only while a position is deposited, time outside the farm does not count. If accounting uses periodic snapshots, a change may take effect at the next snapshot rather than immediately.

Compare the position recorded by the farm with the amount you expect it to recognize, allowing for any share conversion or pool accounting used by the contracts. A wallet can still own the underlying economic exposure while the reward contract records no stake. Fixing that requires satisfying the farm’s deposit conditions; adding more liquidity to the pool will not help if the farm does not count it.

Did the reward rate change, or did the estimate change?

Separate token emissions from the displayed APR. A simplified pool share is the reward allocation assigned to the pool divided among eligible stake according to each participant’s weight. If total eligible stake rises while the allocation stays constant, each unit of stake receives a smaller share. The APR can also move when the reward token’s market price changes or when a frontend changes its price source or calculation window.

Inspect the allocation and eligible-stake values at the same block or time period. Comparing today’s APR with yesterday’s is not enough if either the total stake or token price changed. Check whether the displayed figure assumes compounding, reinvestment or a constant token price; those are modeling choices, not guaranteed returns. A quoted APR can fall sharply while the underlying token emission rate remains unchanged.

For a pool with multiple reward tokens, verify each reward stream separately. One token’s emissions can end while another continues, and a frontend may combine them into a single estimate. Confirm the reward token address and the amount accrued for each stream before concluding that all rewards have stopped.

Can the position harvest the accrued rewards?

Check the claim path independently from accrual. The contract may track pending rewards but require a harvest or claim transaction to transfer them. Review the transaction result: a failed or reverted claim does not demonstrate that nothing accrued. A successful transaction should show the relevant contract call and token transfer, though an explorer’s decoded labels may be incomplete.

If the claim reverts, inspect the revert reason and the contract’s conditions. Possible causes include a paused distributor, a claim restriction, an invalid recipient or a failed token transfer. Avoid repeatedly submitting the same transaction without understanding the failure. A claim can also succeed while the wallet interface remains stale; refresh the token balance or verify the transfer directly on-chain.

Work through the checks in order: confirm active emissions, confirm eligible stake, reconcile the rate inputs, then test the claim path. That sequence separates a program that has ended from a position the farm does not count and from rewards that have accrued but are not displayed. It gives liquidity providers and operators a concrete next step before they withdraw, redeposit or change the position.