Key Highlights
- Uniswap Labs introduced StablePair pools for $USDC/$USDT and $USDC/$USDG on Ethereum with dynamic, direction-sensitive fees.
- The fee mechanism is designed to capture rebalancing income for liquidity providers, but it cannot protect against a token losing its peg or external value.
- Governance controls the benchmark, fee settings, upgrades and roles, while documented hook restrictions limit certain withdrawal-blocking and fee-skimming capabilities.
How Uniswap StablePair’s Dynamic Fee Mechanism Works
Uniswap Labs announced the Ethereum-based $USDC/$USDT and $USDC/$USDG pools on Sept. 10. In an explanation published on Sept. 16, the company said liquidity providers entering the pools are choosing a fee mechanism as well as the token inventory they must hold.
StablePair uses a configured one-for-one reference rate for each pool. The fee logic compares that stored reference with the pool’s price and does not consult an external market-price feed. Within a narrow band around the reference, fees vary according to swap direction so the pool can target a consistent bid and ask before price impact is considered.
When the pool is exactly at its reference price, both trading directions pay the configured optimal fee. As the pool moves toward one edge of the band, the fee declines in one direction and increases in the other. For example, with an optimal fee of one basis point, or 0.01%, a swap involving 10,000 input units at the reference price would generate one input unit in fees for liquidity providers.
Outside the band, StablePair classifies trades according to whether they move the pool farther from or closer to the reference. A trade that moves farther away pays no LP fee, while a trade that pulls the pool back toward the reference faces a declining fee. The design is intended to make corrective trades progressively more attractive as blocks pass. If a trader accepts the fee, liquidity providers collect income while the pool is rebalanced. Uniswap Labs says the mechanism captures the “vast majority” of rebalancing profit.
Block-Level Price Caching Creates Trade-Offs
The first swap in each block caches the pool price used for subsequent fee calculations. This prevents traders from gaining the same-block fee advantage by splitting corrective swaps into multiple transactions. However, later transactions in that block may use stale price information.
If the live pool price crosses the configured reference during a block, the cached classification can temporarily assign fees to the opposite trading directions until the next block. The zero-fee classification therefore depends on the cached price and should not be interpreted as a permanent rule that every sale of a weakening token is free.
StablePair Does Not Remove Peg and Inventory Risk
The central limitation appears when the external market no longer treats the two assets as equal. In a hypothetical issuer-related shock, one coin could lose external value while the configured reference continues to assume a one-for-one exchange rate. Selling the weakening coin for the stronger coin could move the pool farther from its configured reference while moving the pool price closer to the broader market.
In that situation, a trade classified by the fee logic as moving away from the reference could represent genuine price discovery rather than a temporary imbalance. StablePair cannot assess issuer solvency or restore a token’s redemption value. This hypothetical example is not a report of a current depeg, exploit or loss in either StablePair pool.
If a liquidity provider held 10,000 hypothetical coins and their external value fell from $1 to $0.90 each, the inventory would decline in value from $10,000 to $9,000 before fees. Rebalancing income would not automatically reimburse that $1,000 loss.
Trades can also alter the assets held by a liquidity provider. Selling the weaker coin into available liquidity removes the stronger coin and leaves active positions with a larger share of the weaker asset. A trade classified as moving away from the reference and charged no LP fee would provide no fee income to offset that increased exposure. The actual amount exchanged still depends on available liquidity, the provider’s selected range and price impact.
StablePair Pool Activity and Return Evidence
On Sept. 30, the Stats panels in the Uniswap interface showed approximately $6.1 million in total value locked and $117.9 million in 24-hour volume for the $USDC/$USDT StablePair pool at around 15:59 UTC. The $USDC/$USDG pool showed approximately $2.6 million in TVL and $8.7 million in 24-hour volume at around 15:57 UTC.
A same-pair comparison was available through the Ethereum $USDC/$USDT v3 pool charging a 0.01% fee. At approximately 16:02 UTC, that pool displayed about $34.2 million in TVL, $15 million in 24-hour volume and $1,100 in 24-hour fees.
These observations were not synchronized. The pools also have different fee rules and liquidity conditions, while the StablePair panels did not provide a comparable absolute fee total or realized return at the individual-position level.
Assessing whether StablePair produces better returns would require comparable measurement periods, active liquidity ranges, fee income and inventory valuations. Trading volume alone cannot establish whether a liquidity provider performed better than in another pool or than by simply holding the underlying assets.
Governance Controls the Benchmark and Hook Permissions
Under Uniswap’s documented role model, governance controls live fee configurations, implementation upgrades and role administration. Changing the reference rate changes the benchmark used to classify and charge swaps. The deployment documentation directs integrators to read the hook’s live configuration because governance can change its parameters.
Separate restrictions govern what an upgrade can do. The hook’s permanent address permissions exclude remove-liquidity callbacks and custom accounting deltas. According to Uniswap’s security documentation, those restrictions prevent upgrades from using those capabilities to block liquidity-provider withdrawals or alter swap amounts to skim additional fees. The ability to withdraw tokens does not, however, guarantee the market value of the assets received.
Uniswap said OpenZeppelin reviewed the core fee mechanism of a non-upgradeable predecessor from Feb. 9 to 13, 2026. The splitting issue was resolved through block caching, while the later upgradeability and role model were outside that review.
Why This Matters for Liquidity Providers
StablePair changes the economics of supplying liquidity for rebalancing. Its dynamic fees are designed to direct incentives toward trades that restore the pool toward a configured parity and to allow liquidity providers to collect more of the associated rebalancing income.
That mechanism does not eliminate inventory risk, price impact or the possibility that the configured one-for-one benchmark no longer reflects external market value. The core decision for LPs remains whether the assets justify supplying liquidity around that reference and whether the fees earned are sufficient to compensate for the inventory ultimately held.
Frequently Asked Questions
What are Uniswap StablePair pools?
StablePair pools are Uniswap pools that use a configured reference rate and dynamic, direction-sensitive fees. The Ethereum pools discussed are $USDC/$USDT and $USDC/$USDG.
Can StablePair protect liquidity providers from a depeg?
No. The fee mechanism can adjust fees around a configured parity, but it cannot verify issuer solvency, restore redemption value or prevent losses if one token’s external value declines.
Does a zero-fee trade always mean a liquidity provider avoids risk?
No. A trade classified as moving away from the reference may pay no LP fee, but it can still change the provider’s asset mix and increase exposure to the weaker token. The classification also depends on the cached block-level price.