Solc version used (known-bug versions flagged)
Rocket Pool's assessment for RD-F-170 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Two Solidity versions in production. (1) 0.7.6: used for all pre-Saturn core contracts (rETH, RocketStorage, RocketBase, etc.). Active known bug: DirtyBytesArrayToStorage (low severity, affects 0.0.1–0.8.15). Compiler is unsupported (de facto EOL — see F174). (2) 0.8.30: used for Saturn One megapool contracts. Active known bugs: TransientStorageClearingHelperCollision (HIGH severity, 0.8.28–0.8.34) — requires clearing both storage AND transient storage; Rocket Pool megapool contracts DO NOT use transient storage (confirmed by source inspection), so this bug is non-applicable to deployed code. LostStorageArrayWriteOnSlotOverflow (low). Yellow: 0.7.6 has a low-severity bug and is unsupported; 0.8.30 has a high-severity bug in the compiler but triggering conditions are absent.
Sources #
- EtherscanrETH Token Etherscan SourcerETH Etherscan — compiler 0.7.6+commit.7338295f, optimizer 15000 runsretrieved 2026-05-04
- hardhat-common.config.jshardhat-common.config.js — 0.7.6 and 0.8.30 compiler versionsretrieved 2026-05-04
- RocketMegapoolDelegate.solRocketMegapoolDelegate.sol — no transient storage usage confirmedretrieved 2026-05-04
- TransientStorageClearingHelperCollision Bug AnnouncementSolidity blog TransientStorageClearingHelperCollision announcement (0.8.28–0.8.34)retrieved 2026-05-04
Methodology #
Identify the Solidity compiler version used for deployed bytecode and flag if it appears on the known-bug list (solc bugs.json or Vyper 0.2.15–0.3.0 range).
See the full factor methodology and distribution across all protocols →