Solc version used (known-bug versions flagged)
Beefy Finance'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 #
Primary compiler: Solidity 0.8.23 (foundry.toml + hardhat.config.ts); secondary: 0.8.19 (hardhat.config.ts). BIFI token deployed at 0.8.19+commit.7dd6d404 (Etherscan verified). Per etherscan.io/solcbuginfo: 0.8.23 has only VerbatimInvalidDeduplication (Low severity, Yul-only). 0.8.19 same. Neither on high/critical bug list for standard Solidity compilation without viaIR or transient storage. TransientStorageClearingHelperCollision (High) affects 0.8.28-0.8.33 — not applicable to 0.8.23 or 0.8.19.
Sources #
- GitHubbeefy-contracts foundry.tomlfoundry.toml — solc = '0.8.23', optimizer_runs = 200, evm_version = 'cancun', viaIR not setretrieved 2026-05-16
- BIFI Token Etherscan Compiler InfoBIFI token Ethereum 0xb1f1ee126e9c96231cc3d3fad7c08b4cf873b1f1 — compiler v0.8.19+commit.7dd6d404, optimizer 200 runsretrieved 2026-05-16
- Etherscan Solidity Bug Infoetherscan.io/solcbuginfo — 0.8.23: VerbatimInvalidDeduplication (Low) only; no high/critical bugsretrieved 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 →