Solc version used (known-bug versions flagged)
Lombard 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 EVM contracts compiled with Solidity v0.8.24+commit.e11b9ed9 (BridgeV2 implementation, BasculeV2, StakedLBTC). LBTC proxy implementation 0x072072317469ebb6c340a47e41561c9c3b782bd9 compiled with v0.8.20+commit.a1b79de6. Hardhat.config.ts specifies solidity: '0.8.24' as the project-wide compiler. Both 0.8.20 and 0.8.24 are not on the official Solidity known-bug list for high/critical issues relevant to upgradeable token contracts. No Vyper detected (data cache vyper_detected: false). EVM version target: Paris (pre-Cancun) per Etherscan bytecode metadata.
Sources #
- GitHubHardhat config — compiler versionhardhat.config.ts: solidity '0.8.24', optimizer 200 runsretrieved 2026-05-05
- LBTC Implementation Etherscan metadataLBTC impl compiler: v0.8.20+commit.a1b79de6; EVM: Parisretrieved 2026-05-05
- BridgeV2 Proxy Etherscan — impl compiler versionBridgeV2 impl compiler: v0.8.24+commit.e11b9ed9retrieved 2026-05-05
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 →