Dynamic liquidity pool fees can change with a pool’s state, but that does not make them a forecast of what a liquidity provider will earn. On September 10, 2026, Uniswap Labs introduced StablePair Hook for stable pairs. The useful lesson is broader than the launch: before changing a position, separate the fee mechanism, the exact pool, the quote context, and your own position evidence. For pools listed in its Liquidity workspace, Gimmer exposes current pool identity and account-specific position and activity evidence; keep quote context as a separate check. It does not turn an external protocol announcement into a recommendation or a promised return.
What Uniswap launched on September 10
Uniswap Labs announced StablePair Hook as a Uniswap v4 dynamic-fee hook for stable pairs. Its first two named pools are USDC/USDT and USDC/USDG on Ethereum. The official Uniswap hook repository records both pool IDs as initialized on September 10 with the dynamic-fee flag.
The mechanism is specific. A StablePair pool has a reference rate and a narrow band around it. According to the StablePair developer overview, the hook sets the LP fee from the pool’s distance from that reference and the direction of the swap.
Inside the band, the fee adjusts to maintain a configured bid/ask spread before the swap’s own price impact. Outside the band, a swap moving the price farther from the reference pays no fee, while a corrective swap faces a fee that decays block by block until someone accepts the opportunity. That describes how a swap is charged. It does not describe the total fees in one LP position, the value of that position, or what happens next.
How dynamic liquidity pool fees change the reading order
A fixed fee can be written as one number on a pool card. A dynamic fee requires a more careful question: which fee would apply to this direction, from this pool state, at this time?
Even that answer is incomplete. Uniswap’s dynamic-fee documentation distinguishes the fee from price impact. A large swap can still move through the curve and receive a different average execution price from a small one. The mechanism also depends on pool-specific configuration that governance can change.
This creates three common category errors:
- Mechanism becomes outcome: “dynamic” is interpreted as “higher earnings.” It only says the rule can change.
- Pair becomes pool: a USDC/USDT headline is assumed to apply to every USDC/USDT pool, regardless of network, protocol version, hook, or pool ID.
- Pool fee becomes position fee: the fee charged on a swap is confused with the claimable fees accumulated by one wallet position.
The cure is not another headline number. It is keeping four records separate.
A four-record evidence card for an LP decision
Before adding, keeping, or removing liquidity, write one row for each layer:
| Record | What to capture | What it cannot prove |
|---|---|---|
| 1. Mechanism | Protocol version, hook or fee model, reference source, and when you checked it | Your realized fees or position value |
| 2. Exact pool | Network, pair, pool ID, current fee configuration, and whether this is the announced pool | That another pool with the same pair behaves identically |
| 3. Quote context | Direction, size, time or block, price impact, gas, and route | What a later quote will show |
| 4. Your position | Remaining token amounts, claimable fees, update time, and recent transaction state | Future fees, protection from loss, or a complete market valuation |
This card extends the same discipline used when you reconcile delayed balance data before rebalancing: identify the timestamp and source of each number before allowing it to drive an action.
What Gimmer can show for a listed liquidity pool
Gimmer’s current Liquidity workspace gives each listed pool a concrete identity. It shows the pair and network, the Uniswap protocol version and fee tier when reported, and the on-chain pool ID when the server provides it. That is the place to test whether an external headline even refers to the pool in front of you.
The workspace then keeps position evidence separate. Your liquidity shows remaining token amounts, claimable fees, and the last update time after network recovery completes. Activity presents the latest liquidity-related wallet transactions from its bounded last-24-hours view, including status and an explorer link when the transaction reference is safe to open.
If you are preparing a deposit, the Amount → Review → Confirm flow requires both tokens and shows reviewed maximum token inputs, network-cost bounds, and price tolerance before authorization. That review is about the exact Gimmer-listed pool and the current account. It is not evidence about every pool carrying the same token symbols.
For a fuller reading routine, use the existing guide to read liquidity activity and pool signals before a position change, then verify the transaction itself using the wallet-activity evidence checklist.
What the Gimmer view cannot decide
The StablePair launch does not mean its pools are available inside Gimmer. Gimmer’s Liquidity workspace covers the pools it currently lists; a matching token symbol is not a matching pool.
The product also does not promise that a displayed fee tier, historical APR, TVL, or volume will continue. Pool metrics may be unavailable, and they are not a deposit quote. The current deposit review does not assess whether the pool price is fair against an independent market reference. A position can lose value, network costs still apply, and fees are not guaranteed.
If pool or position data is recovering, stale, or unavailable, do not translate the missing record into zero. Retry the read or pause the decision. The Gimmer overview documentation is a useful starting point for understanding how the product separates current account state from actions.
A worked example: the pair matches, but the pool does not
Imagine Maya reads the StablePair announcement and already has exposure to a stablecoin pair. She writes “USDC/USDT” at the top of her evidence card, then stops. That pair name alone does not answer the decision.
- She records September 10 as the event date and links the Uniswap mechanism documentation.
- She compares network, protocol version, hook, and pool ID. If any field differs, she marks the announcement as market context rather than a rule for her position.
- She obtains a fresh quote for the direction and size she actually cares about, keeping fee, price impact, and network cost in separate columns.
- If the pool is listed in Gimmer, she records the shown pool identity, position update time, remaining token amounts, claimable fees, and latest activity status.
- She changes nothing while one of those records is missing or recovering.
The outcome may be “no action.” That is still a useful result: the announcement has been scoped without pretending that a new fee design automatically improves an unrelated position.
Questions liquidity providers are likely to ask
Are dynamic fees the same as variable APR?
No. A dynamic fee is the rule that determines the fee charged on a swap. APR is a historical or estimated rate derived from activity and other assumptions. Neither one guarantees what a particular LP will earn.
Does every Uniswap v4 pool now use StablePair fees?
No. StablePair is a specific hook with specific initialized pools and configuration. Verify the network, hook, and pool ID instead of carrying its rules to another v4 pool.
Can Gimmer tell me whether a StablePair position is suitable?
No. Gimmer can expose identity and account-specific evidence for pools available in its current Liquidity workspace. It does not certify an external pool, forecast its fees, or replace an independent review of token, contract, market, and liquidity risks.
Separate the rule before you act
Uniswap’s StablePair launch is a clear example of fees becoming state-dependent. The practical response is not to compress that mechanism into a yield claim. Keep the rule, exact pool, quote context, and personal position as four different records.
Download Gimmer, open Liquidity, and record the listed pool’s identity, shown fee tier, position update time, claimable fees, and latest transaction status before you decide whether to add or withdraw liquidity.
— The Gimmer Team