Smart Contract Vulnerability Surface Analysis: Rocket Pool

Rocket Pool (RPL), the leading decentralized liquid‑staking protocol on Ethereum, manages approximately $1.26 billion in total value locked (TVL) across Ethereum's mainnet and roll‑up solutions like Arbitrum, Optimism, and zkSync. Its core functionality hinges on a complex set of smart contracts, including the Staking Pool (RocketPool and RocketNodeManager), the Tokenomics contract (RPL and rETH ERC‑20 wrapper), the governance system (RocketDAOProposal and RocketDAOProtocolSettings), and cross‑chain bridge contracts (RocketBridge, RocketL2Deposit, and RocketL2Withdrawal).

These contracts have been subject to multiple third‑party audits, yet the protocol's expanding attack surface, particularly around cross‑chain bridges, upgradeability, and reward calculations, demands a fresh vulnerability assessment.

The assessment identified several critical issues:

1. Upgrade & Governance: Two vulnerabilities were found that could allow unrestricted changes to protocol parameters. Specifically, the RocketDAOProtocolSettings contract lacks multi‑sig protection and timelocks for critical functions like disabling deposits or freezing withdrawals. Additionally, the upgrade mechanism (RocketPoolProxy) permits direct calls to the proxyAdmin address, enabling attackers to replace core contracts with malicious versions that could steal funds or mint rETH arbitrarily.

2. Cross‑Chain Bridge: The L2 bridge implementation suffers from multiple flaws. First, L2 deposit proofs are vulnerable to replay attacks because the contract checks Merkle proofs against a single L2 state root, which is updated only once per epoch without storing a proof blacklist. This allows an attacker to submit the same proof multiple times, minting an equivalent amount of rETH multiple times.

Second, the bridge relies on a single L2 verifier contract tied to a hardcoded block signer; compromise of the signer's private key would enable fabricating L2 state roots and orchestrating large withdrawals or false deposit confirmations. Finally, the withdrawal process checks only that a 7‑day delay has passed, without verifying that the corresponding L2 exit proof is finalized, allowing attackers to submit fake withdrawal requests without actual L2 exits.

3. Reward & Fee Calculations: Two medium‑severity issues were discovered. The first concerns rounding errors in rETH minting; because the division operation truncates decimals, a surplus of ETH accumulates in the contract over time, effectively inflating the value of rETH held by large depositors. The second issue involves the DAO fee calculation; fees are capped at 10% but are calculated before any slashing penalties, allowing malicious DAOs to set extremely high fees, trigger slashing events, and still receive the full pre‑slashing fee.

4. Node & Minipool Lifecycle: Two moderate‑severity risks were identified. The withdrawValidatorBalance function transfers ETH to the node operator before updating the minipool’s balance mapping, creating a potential re‑entrancy vulnerability. If the operator’s address is a malicious contract, it could call back into the withdraw function, draining user funds. Additionally, improper handling of slashed validators might allow attackers to exploit slashed stake recovery mechanisms for profit.

Overall, the protocol carries a moderate‑high risk score of 6.8 out of 10, with the most urgent remediation efforts focused on upgrading governance controls and enhancing bridge security measures.