Uniswap v4 went live on January 31, 2025, according to the official Uniswap Labs announcement. It launched on Ethereum plus nine other networks that day, including Base and Arbitrum — the two venues many concentrated-liquidity LPs already watch for gas and flow. This piece is a practical LP briefing: what actually changed versus Uniswap v3, how hooks and dynamic fees alter the risk surface, and a checklist you can run before minting into a v4 pool.
Nothing here is a yield forecast. Concentrated liquidity still means inventory risk and impermanent loss; v4 mainly changes the programmable layer around that tradeoff.
What Uniswap v4 kept from v3
At the core, v4 still uses the concentrated liquidity model introduced in Uniswap v3: LPs choose price ranges, capital is denser inside those ranges, and positions can go inactive when price leaves the band. If you already understand tick ranges, fee accrual while in-range, and out-of-range inventory drift, that mental model still applies.
The Uniswap v4 whitepaper and developer docs frame v4 as an extensible AMM built on that foundation — not a return to full-range constant-product pools. For an Arbitrum LP or Base DeFi LP migrating a familiar pair, the first question is not “is this still concentrated liquidity?” It is “what extra logic rides along with this pool?”
The three architecture changes LPs should name
1. Singleton PoolManager
Uniswap v4 stores pool state in a singleton-style PoolManager rather than one
contract per pool (see
Uniswap/v4-core and the
v4 whitepaper).
Integrators unlock the manager, run actions such as swap or modifyLiquidity, then settle net
balances. For LPs, the UX implication is that routing and position tooling matter more than
memorizing a per-pool factory address — and that “which app minted this position?” becomes
part of operational hygiene.
2. Flash accounting
Flash accounting nets token deltas inside an unlock window instead of transferring after every intermediate step. Uniswap Labs’ launch post cites gas savings on multi-hop swaps and states that creating new pools can be up to 99.99% cheaper than in prior versions (Jan 31, 2025). Cheaper pool creation does not mean “more TVL is always better for you” — it can also mean more experimental pools with thin flow. Treat new tickers as research projects, not default deposits.
3. Native ETH
v4 supports native ETH without mandatory wrapping for ETH pairs (whitepaper / architecture docs). That can reduce friction for ETH-denominated LPs, but it does not change the economic fact that pairing ETH with a volatile asset still exposes you to divergence loss when prices move.
Hooks: the feature that rewrites LP diligence
Hooks are external contracts attached at pool initialization. They can run before/after initialize, add/remove liquidity, swap, and donate. The set of which callbacks a pool uses is fixed at creation; the callback logic depends on the hook implementation (v4-core README).
Uniswap Labs’ launch post said more than 150 hooks had already been developed by launch day, spanning ideas like dynamic fees and automated liquidity management. For an LP, that diversity is both the opportunity and the hazard: two pools with the same token symbols can behave like different products once hooks differ.
Practical diligence questions before you LP a hooked pool:
- Who wrote the hook, and is the source verified on the explorer?
- Which lifecycle flags are active? (Especially beforeSwap / afterSwap and liquidity hooks.)
- Does the hook take its own fee or custom accounting deltas? Hook fees are distinct from LP swap fees in Uniswap’s dynamic-fee docs.
- Is the hook upgradeable or gated? Permissioned or admin-controlled logic changes your counterparty model.
- Has the hook been audited? Core v4 underwent nine audits and a large bug bounty per Uniswap Labs; that does not automatically extend to every third-party hook.
Dynamic fees vs Uniswap v3 fee tiers
Uniswap v3 popularized static fee tiers (commonly discussed as 0.05%, 0.30%, 1.00%, with
additional tiers in practice). Uniswap v4 can still use fixed fees, but it also supports
dynamic fees: pools initialized with the dynamic-fee flag can have LP fees
updated periodically via updateDynamicLPFee, or overridden per swap from a
beforeSwap hook
(Uniswap developer docs: Dynamic Fees).
For LPs, dynamic fees are not automatically “higher APR.” They are a policy. Volatility-linked fees may rise when informed flow is aggressive; volume-linked policies may cut fees to win flow. Official docs list many design patterns (volatility, volume, time-of-day, oracle-relative pricing, and more). Your job is to understand which policy a pool uses and whether that policy aligns with your holding period.
On Base DeFi and Arbitrum, you will also see community hook submissions that advertise volatility-responsive or IL-aware fee logic. Treat marketing claims as unverified until you read the contract and fee path yourself — and never invent expected returns from a tagline.
Base and Arbitrum: same protocol, different LP context
Because v4 is live on both Base and Arbitrum (per the Jan 31, 2025 launch list), LPs should still compare venues the old-fashioned way:
- Gas and rebalance cadence. Lower L2 gas makes active range maintenance cheaper, but it also tempts over-trading.
- Competing venues. On Base, Uniswap coexists with Aerodrome-style incentive markets; on Arbitrum, depth and routing habits differ by pair.
- Hook ecosystem maturity. A hook that is liquid and well-reviewed on one chain may be a thin experiment on another.
Do not assume a “v4 ETH/USDC” experience is portable across chains without checking local volume, hook address, and fee policy.
What did not disappear: impermanent loss and range work
Hooks can automate rebalancing, change fees, or add order-like behavior, but they do not repeal the inventory math of concentrated liquidity. If price trends through your range, you still end up holding more of the underperforming asset relative to a simple hold of the starting mix — the classic impermanent loss / divergence story. Automation can reduce operational friction; it can also concentrate risk if the rebalance policy is aggressive or poorly parameterized.
A durable LP strategy still needs three ledgers: expected fee income, expected divergence, and operating friction (gas, swaps to re-center, hook fees). v4 mainly expands the third ledger and the fee-policy dial.
Practical takeaway for LPs
Before minting into a Uniswap v4 pool on Base or Arbitrum, run this five-minute gate:
- Confirm the pool is actually v4 (PoolManager / hook address visible in the UI).
- Read the hook’s verified source and list of active callbacks.
- Determine whether fees are static or dynamic — and what inputs drive changes.
- Map your range width and rebalance plan as if the hook might fail or pause.
- Size the position as experimental capital until you have live fee and inventory history.
If you cannot explain the hook in one plain sentence, you are not LPing Uniswap — you are underwriting an unnamed strategy contract that happens to sit next to a liquidity pool.
Sources (dated)
- Uniswap Labs, “Uniswap v4 is Here,” Jan 31, 2025 — blog.uniswap.org
- Uniswap v4 whitepaper PDF — app.uniswap.org/whitepaper-v4.pdf
- Uniswap developer docs, Dynamic Fees — developers.uniswap.org
- Uniswap/v4-core repository — github.com/Uniswap/v4-core
Bottom line
Uniswap v4 keeps concentrated liquidity and adds a programmable surface — hooks, a singleton manager, flash accounting, optional dynamic fees, and native ETH — now available on Base, Arbitrum, and the other launch chains named by Uniswap Labs on January 31, 2025. For LPs, the upgrade is less “new yield button” and more “new diligence checklist.” Learn the hook, name the fee policy, and keep impermanent loss in the same worksheet you used on v3.