Liquid Restaking Token (LRT) Arbitrage 2026: eETH, ezETH, rsETH Playbook
**Answer first** — LRT (Liquid Restaking Token) arbitrage in 2026 captures spreads between LRTs like weETH, ezETH, rsETH, pufETH and their underlying ETH/stETH. With $30B+ TVL acro

Answer first — LRT (Liquid Restaking Token) arbitrage in 2026 captures spreads between LRTs like weETH, ezETH, rsETH, pufETH and their underlying ETH/stETH. With $30B+ TVL across the LRT ecosystem and frequent peg drift during yield rebalancing events, the arb pays consistently for searchers running atomic bundles on Curve, Uniswap V3, Balancer, and Pendle pools. The playbook is structurally similar to stablecoin depeg arb but with LRT-specific risks: AVS slashing exposure, sequential withdrawal queues, and correlation between LRT depegs and systemic restaking stress.
The 2026 LRT Landscape
Five LRT protocols dominate the market:
| Protocol | Token | TVL (May 2026) | Backing |
|---|---|---|---|
| ether.fi | weETH | ~$10B | EigenLayer restaked ETH |
| Renzo | ezETH | ~$3B | EigenLayer + Symbiotic |
| Kelp DAO | rsETH | ~$1.5B | EigenLayer |
| Puffer | pufETH | ~$1B | EigenLayer + native restaking |
| Swell | rswETH | ~$800M | EigenLayer |
Together with smaller LRTs (mETH, weEthx, others), total LRT TVL exceeds $30B. The market is liquid enough for atomic arbitrage to clear profitably but fragmented enough that pricing inefficiencies persist for seconds-to-minutes.
Where The Spread Actually Comes From
LRT peg drift has predictable causes:
1. Yield reset events
LRTs distribute restaking yield periodically. The moment before/after a yield update, the LRT trades at a slightly stale price vs. the new NAV. Arb closes the gap.
2. Large mint/redemption flows
A whale minting $100M worth of ezETH compresses the price marginally vs ETH on Curve. The next 30 seconds offer arb back to par.
3. Cross-DEX route congestion
weETH/ETH price on Curve may diverge from the same pair on Balancer or Uniswap V3 during gas-fee spikes. Atomic bundles capture the cross-venue spread.
4. Sentiment-driven depegs
Negative news on EigenLayer or a specific AVS triggers panic selling of one LRT. The depeg can be 1-3% briefly. This is the dangerous one — see Risk section.
Strategy 1: Cross-DEX Atomic Arbitrage
The bread-and-butter LRT arb. Standard atomic pattern:
- Monitor weETH/ETH price across Curve, Uniswap V3, Balancer, Pendle
- When spread > gas + 0.1% threshold, build atomic bundle: buy cheap side, sell expensive side
- Submit through Flashbots private relay
- Capture spread minus gas
Realistic per-trade profit on weETH/ezETH/rsETH:
- Quiet hours: $5-$50/trade, 10-30 opportunities/day
- Active flow: $50-$500/trade, 30-100 opportunities/day
- Reset events (oracle/yield updates): $200-$2,000/trade, 2-8 opportunities
The competitive moat is fast simulation against the actual LRT pool math (Curve's stable invariant, Uni V3's tick math) for the current block state. Generic price-spread bots that don't account for slippage curves on shallow pools will mispriced.
Strategy 2: LRT-to-LRT Triangular Arbitrage
LRTs don't always move together. When weETH appreciates 0.2% but ezETH stays flat, the implied weETH/ezETH cross-rate diverges from observed market.
The bundle:
- Sell weETH for ETH
- Buy ezETH with ETH
- Sell ezETH for weETH (or original equivalent)
If the final balance exceeds the starting balance net of fees, the triangle was profitable. Per-trade profits are smaller (10-100 bps gross) but opportunity frequency is high during volatile periods because LRTs respond to news at different speeds.
See Cross-Chain Arbitrage MEV 2026 for the cross-chain extension of this pattern (some LRTs trade on multiple chains).
Strategy 3: Pendle PT/YT Arbitrage
Pendle splits LRTs into Principal Tokens (PT) and Yield Tokens (YT). Periodic mispricing between PT + YT vs the underlying LRT creates arb:
weETH price ≠ PT-weETH price + YT-weETH price
When the equation breaks, atomic arb between Pendle and Curve closes the gap. This is a more sophisticated play — requires modeling Pendle's AMM curve (uses generalized AMM with implied yield) — but yields better win rates because fewer searchers run Pendle-aware bots.
Strategy 4: Redemption Arbitrage (Non-Atomic)
When an LRT trades meaningfully below par for hours:
- Buy LRT at discount on DEX (e.g. ezETH at 0.985 ETH)
- Queue redemption with the protocol
- Wait 1-7 days for withdrawal
- Receive ETH at par
Risks during the holding period:
- ETH price moves (your ETH-denominated profit is fine; USD-denominated may differ)
- LRT could depeg further (mark-to-market loss)
- Withdrawal queue could extend (longer holding period)
This is a portfolio strategy, not a searcher strategy. Capital is unproductive during the queue. Only viable when the depeg is large enough (>0.5%) to clear protocol risk premium.
Risk 1: AVS Slashing Cascade
The biggest unique LRT risk: an AVS (Actively Validated Service) on EigenLayer gets slashed, the loss propagates to the underlying restaked ETH, and the LRT's NAV drops. Multiple LRTs are exposed to the same set of AVSs.
If you're holding LRT inventory for redemption arb during a slashing event, your "depeg arbitrage" turns into "buying the dip on a permanent capital impairment." See the stablecoin depeg algorithmic collapse warning for the analogous trap.
Defense:
- Never hold a single LRT >30% of working capital
- Monitor AVS slashing events on EigenLayer's dashboards
- Pause LRT arbitrage during major slashing events for at least 72 hours
Risk 2: Smart Contract Risk Stack
LRT arb stacks multiple contract risks:
- The LRT protocol itself
- The underlying EigenLayer / Symbiotic restaking layer
- The DEX pool you're trading on
- Any router contract in the path
A single exploit anywhere in the stack can drain your inventory. Whitelist LRTs whose protocols have been audited and are >6 months in production. New LRTs (<3 months mainnet) are too risky for serious capital.
Risk 3: Liquidity Concentration
LRT liquidity is shallower than ETH/USDC. Big trades face material slippage on most pools outside the top 3 (Curve weETH/ETH, Curve ezETH/ETH, Balancer weETH/wETH). The arb size cap is usually $50k-$200k per trade — beyond that, slippage eats the spread.
Realistic Returns
Indicative early-2026 monthly returns for a solo searcher with $50k working capital running LRT arb:
- Quiet month (no yield events, no depeg): 1.5-3%
- Active month (multiple yield resets, normal flows): 4-9%
- Volatility-spike month: 6-15% (gross), but with larger drawdown tail risk
Returns are illustrative. The strategy is in a sweet spot in 2026: large enough TVL to support real size, competitive but not saturated like Uniswap V2 arb, and the LRT-specific knowledge filters out generic bots.
See the FRB risk disclosure for full risk model.
Infrastructure Requirements
To compete in LRT arbitrage:
- Low-latency mainnet RPC with mempool access. See Best Private RPC for Ethereum.
- Fork simulator that handles Curve stable invariant + Uni V3 tick math + Pendle's implied-yield AMM
- Per-protocol monitoring: AVS slashing dashboards, withdrawal queue depths, yield rebalance schedules
- Flashbots private relay for bundle submission
FRB Agent handles the atomic-arb leg natively. The strategy-selection logic (which LRT to focus on, when to pause for AVS events) stays manual — that's judgement, not execution.
What FRB Agent Does
FRB Agent's atomic-arbitrage engine works on LRT pools the same way it works on stablecoin pools — Curve, Uniswap V3, Balancer pools are first-class supported on Ethereum mainnet. Configure your LRT pools as contracts in the dashboard, set per-trade caps, and the engine handles bundle construction.
What it does not automate:
- AVS slashing event detection (manual, requires off-chain monitoring)
- Redemption queue arbitrage (asynchronous, not a bundle workflow)
- Pendle PT/YT triangulation (requires custom routing not yet in default routers)
Further Reading
Step after reading
Launch FRB dashboard
Connect your wallet, pair the node client with a 6-character PIN, and assign the contract mentioned above.
Need the signed build?
Download & verify FRB
Grab the latest installer, compare SHA‑256 to Releases, then follow the Safe start checklist.
Check Releases & SHA‑256Related Articles
Further reading & tools
Discussion
No notes yet. Add the first observation, or share the link with your team on X (@MCFRB).