Solc version used (known-bug versions flagged)
Hyperlane'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 solc versions: (1) Deployed Mailbox (Ethereum + BSC): v0.8.19+commit.7dd6d404 — no known high/critical bugs. (2) Current foundry.toml build toolchain: solc 0.8.33, evm_version cancun. Etherscan solcbuginfo lists HIGH severity 'TransientStorageClearingHelperCollision' bug affecting 0.8.28–0.8.33 (fixed in 0.8.34). Hyperlane uses evm_version cancun enabling transient storage opcodes. New contracts deployed with 0.8.33 + cancun inherit this bug until upgrade to 0.8.34. Score: yellow (deployed production at 0.8.19 clean; build toolchain at 0.8.33 carries HIGH bug applicable to new cancun deploys).
Sources #
- EtherscanEthereum Mailbox v3 Implementation — Etherscan (compiler metadata)Mailbox impl 0x7b4D881c122a5e61adCFfb56A2e3CE9927D53455 — compiler v0.8.19+commit.7dd6d404, no known bugsretrieved 2026-05-17
- Hyperlane Monorepo — foundry.toml (solc 0.8.33 + cancun)foundry.toml — solc 0.8.33, evm_version cancun, optimizer_runs 10000retrieved 2026-05-17
- Solidity Compiler Bug Information — EtherscanEtherscan solcbuginfo — TransientStorageClearingHelperCollision: HIGH, 0.8.28–0.8.33, fixed in 0.8.34retrieved 2026-05-17
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 →