Solc version used (known-bug versions flagged)
StakeWise v3's assessment for RD-F-170 — scored green on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
foundry.toml specifies solc 0.8.26 with evm_version = cancun for the default profile. Etherscan confirms VaultsRegistry and Keeper compiled with v0.8.22+commit.4fc1097e; VaultFactory and newer contracts compiled with v0.8.26+commit.8a97fa7a. Etherscan solcbuginfo confirms no high-severity known bugs in either version. The high-severity TransientStorageClearingHelperCollision bug first appears in 0.8.28 and does not affect 0.8.22 or 0.8.26.
Sources #
- EtherscanVaultsRegistry Etherscan — compiler versionVaultsRegistry 0x3a0008... compiler v0.8.22+commit.4fc1097e; VaultFactory 0x7A8cbBf... compiler v0.8.26+commit.8a97fa7aretrieved 2026-05-16
- StakeWise v3-core foundry.tomlfoundry.toml: solc = 0.8.26, evm_version = cancun, via_ir = true, optimizer = true, optimizer_runs = 200retrieved 2026-05-16
- Etherscan Solidity Compiler Bug InfoEtherscan solcbuginfo — no high-severity bugs for 0.8.22 or 0.8.26; high-severity bug TransientStorageClearingHelperCollision first appears in 0.8.28retrieved 2026-05-16
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 →