[Report] Rocket Pool Staked ETH (rETH) Status Update

[signal]

This proposal serves as a response to several key questions regarding rETH.

rETH Liquidity Concerns

Historically, rETH’s primary liquidity was concentrated on Balancer. However, a hack last year significantly impacted this liquidity. Through targeted incentives, we have managed to recover liquidity to $7M, though this still trails the $40M level seen prior to the incident.

The situation was further complicated by the rsETH event. Due to the Balancer hack, rETH pools migrated to Balancer V3, which supports “boosted” pools. This means ETH within the LP is deposited into Aave to generate additional yield. While this initially affected rETH/ETH liquidity depth, we expect depth to recover as Aave continues its restoration process. Currently, the IMC (Incentives Management Committee) has increased incentives and is actively seeking additional methods to bolster liquidity.

Chainlink Price Feeds

There was previous consideration regarding the decommissioning of certain feeds due to operational costs. However, given the broad impact such a move would have, the team and the DAO have officially decided to continue supporting these feeds to ensure ecosystem stability.

Recent Upgrades and Roadmap

rETH recently implemented the 4-ETH bond node requirement. This significantly improves ETH capital efficiency and expands the available node supply. Upcoming updates will enable rETH stakers to burn rETH directly and focus on optimizing the performance of decentralized nodes. These improvements are expected to further drive both the supply of rETH and its overall staking yield.

---

Since its launch in 2021, rETH has remained steadfast in its commitment to decentralization. This focus means the protocol maintains a lean treasury, as the majority of ETH staking rewards are distributed directly to stakers and node operators. Despite this, rETH continues to offer the highest levels of security and decentralization among all LSTs (Liquid Staking Tokens).

Finally, we would like to express our gratitude to ETH+ for their steadfast support over the years. We welcome any questions or feedback from the community.

[robtg4]

Useful update. But three things in this report need significantly more attention from the Reserve community before ETH+ allocation decisions are made.

---

1. $7M in pool depth is a vulnerability, not a recovery.

• Pre-Balancer hack: $40M rETH/ETH pool depth.
• Post-hack recovery with incentives: $7M.
  That’s an **82.5% reduction** in available liquidity, and the report frames it as progress.

For an LST that serves as collateral in the ETH+ basket, liquidity depth directly determines three things:

• Rebalancing capacity: How quickly can ETH+ rebalance its rETH allocation under stress without moving the rETH/ETH rate? At $7M depth, a meaningful rebalance event creates its own slippage — the act of rebalancing degrades the price you’re rebalancing at.
• Redemption throughput: ETH+ holders redeeming during a market event need the underlying collateral to be liquidatable at par. $7M in pool depth means any significant redemption wave creates tracking error between ETH+ and its underlying.
• Composability confidence: Other protocols evaluating rETH as collateral (Aave, Morpho, Spark) use liquidity depth as an input to risk parameters. $7M constrains the supply caps and LTV ratios those protocols are willing to assign, which limits rETH’s utility as DeFi collateral.

The IMC “increasing incentives and actively seeking additional methods to bolster liquidity” is the correct response, but the community should be clear-eyed: $7M is not a recovery level. It’s a vulnerability.

2. Balancer V3 boosted pools introduce a new dependency channel — and the Kelp incident just demonstrated why that matters.

The migration to Balancer V3 “boosted” pools — where idle ETH in the rETH/ETH LP is deposited into Aave to generate additional yield — sounds like a capital efficiency upgrade. It is. It’s also a contagion channel.

Twelve days ago, the Kelp/rsETH exploit (April 18, ~$292M bridge hack) spiked borrowing rates across Aave ETH lending markets as leveraged positions unwound simultaneously. Any pool architecture that depends on Aave as a secondary yield layer is now partially coupled to Aave’s lending market health. If Aave experiences stress — another rsETH-type event, a major liquidation cascade, or a temporary market freeze — the boosted portion of rETH/ETH pools is directly affected.

We saw this twelve days ago. Lido’s EarnETH vault had $21.6M in rsETH exposure through Aave. GGV’s looped staking strategies were pushed to negative yield by the same borrowing rate spikes. Boosted Balancer pools using Aave as the yield layer face identical exposure.

The report should explicitly address: what percentage of the rETH/ETH pool is boosted through Aave, and what happens to that liquidity if Aave freezes the relevant market?

3. The 4-ETH bond reduction is the most important structural change in this update — and the report underweights it.

Moving from 8 ETH (previously 16 ETH) to 4 ETH per minipool is not an incremental improvement. It fundamentally changes Rocket Pool’s operator economics:

• Capital efficiency doubles: Each operator can run 2x the minipools with the same ETH commitment. This directly increases rETH supply capacity.
• Operator pool expands: The 4 ETH barrier is accessible to a significantly larger population of potential node operators. More operators = better geographic and infrastructure decentralization — which is rETH’s primary differentiator against Lido.
• Staking yield improves: Lower bond requirements with the same commission structure means higher effective yields for operators, attracting more participants.

For Reserve, this matters because operator decentralization is the security property that distinguishes rETH from centralized alternatives. The more operators, the harder it is for any single entity to affect rETH’s backing.

---

Where Rocket Pool sits in the Tokédex analysis:

I analyzed 58 DeFi protocols through 25 standardized frameworks for the Tokédex. Rocket Pool ranks #1 out of 3 in the Liquid Staking category with a composite score of 75.39 — classified as SAFE.

The scorecard:

Dimension	Score	Analysis
Stakeholder Architecture	5/5	Three-tier alignment: rETH holders earn staking yield, node operators bond RPL collateral (4-150% of ETH value), protocol captures commission. Each stakeholder group has distinct economic incentives that reinforce the others.
Demand Architecture	5/5	Mandatory operator bonding creates structural demand for RPL. Higher RPL ratios = higher commission rates. Operators literally cannot run nodes without RPL collateral — this is genuine demand engineering, not speculative utility.
Distribution & Launch	5/5	Fair launch with no premine. Tokens distributed through beta participation and community building over multiple years. One of the cleanest launches in DeFi.
Governance	5/5	pDAO with no admin keys. Fully decentralized governance with no single points of failure. No centralization risk.
Supply Architecture	4/5	20M RPL cap with 5% annual inflation directed to operators as security incentives. No buyback mechanism but inflation is purpose-directed.
Health Metrics	5/5	TVL/MC ratio of 33.6x ($1.4B TVL, $41.6M market cap). Demonstrates genuine protocol utility over speculation.

Full analysis: Tokédex — The Tokenomic Bible | 800+ Pages, 60 Protocol Analyses

---

One thing to watch: the Saturn upgrade.

The report mentions “upcoming updates” but doesn’t address whether Saturn preserves mandatory RPL bonding for all operator tiers. If future upgrades reduce RPL bond requirements further or introduce operator tiers where RPL bonding is optional, it would weaken the structural demand mechanism that makes RPL tokenomics function. The Reserve community should explicitly ask: does Saturn maintain the requirement that all node operators bond RPL?

The answer to that question determines whether RPL’s demand architecture remains a 5/5 or degrades.

— Robby Greenfield | Author, TOKEDEX: The Tokenomic Bible

[ham]

@signal Thank-you for taking the initiative to put this together and share it on the forum. The level of reporting is appreciated and sets the bar for other collateral providers in the ecosystem.

@robtg4 I came here to respond after reading the post late last week and found most of my points already covered. Thank-you for your comments and welcome to the Reserve Governance forum. I hope you stick around. I’d love to connect properly, could you drop me a message on TG? @hamdefi

---

While an ongoing rETH allocation within the basket strongly aligns with some elements of the mandate, it’s decentralised infrastructure being key among them, I do have some concerns. The chief amongst them being the yield profile, which continues to trail the market rate and the fragility of rETH liquidity especially during market stress. Your comments on these two topics go some way to address them but unfortunately I agree with @robtg4, they aren’t completely alleviated.

1. Liquidity

While I disagree with @robtg4 that Boosted Balancer Pools face identical exposure to looped positions such as those within Lido’s EarnETH vault, the LP’s dependency on Aave’s market health remains. For example during the rsETH hack we saw the LPs TVL fall from $7m down to $4.9m. Unfortunately we’ve also seen no meaningful recovery since with TVL stabilising today around $5m. While it’s easy to contribute cause to some of the largest DeFi hacks our industry has endured, this trend for rETH is concerning.

Another concern I have around rETH liquidity is the apparent dependency on the RockSolid rETH Vault to supply liquidity into this position. Prior to the hack their capital made up roughly 15% of the entire pools TVL. While heavily aligned with the protocol they still have their obligations to vault LPs and pulled their position during the recent market stress, leaving rETH liquidity extremely thin. It is also notable that this capital has not yet returned. While this remains an accessible source of capital for Rocket Pool to re-engage, the dependency on a single allocator, combined with underlying exposure to aETH, introduces additional fragility that should not be relied upon as a primary liquidity backstop.

I’d like to ask for further clarity on the efforts to rebuild rETH liquidity, as Rob said we’ve seen a significant reduction in executional depth in the last 6 months and given the stabilisation we’re seeing, current liquidity rebuilding efforts aren’t sufficient.

That being said, the April liquidity Analysis, completed as the market is starting to recover from the rsETH hack shows that rETH is far from the redemption bottleneck. Only starting to contribute to total basket slippage when ETHplus redemption sizes exceed 30,000. For comparison ETHx liquidity (the current bottleneck) is exhausted at 5,000 ETH. This is great as we enter ‘normal market conditions’ once again but the risk still remains during periods of Aave or wider market stress.

2. Yield

@signal your comments, along with @robtg4’s, are helpful but do not yet provide a sufficient basis for ETHplus governors to rely on when assessing potential basket changes. I’d like to ask for further clarity on the expected increase to the yield profile of rETH.

From the April liquidity report, it is clear the basket is currently out of alignment with its mandate, with ETHplus underperforming its yield benchmark, stETH. While there are external factors contributing to this, including the increase in take rate from 5% to 10%, rETH is also acting as a notable drag on overall yield.

Are there any additional materials, forward yield projections, or timelines for the proposed upgrades that can help governors better assess the expected improvement in rETH’s yield profile?