Solc version used (known-bug versions flagged)
Liquity V1 + V2 (LUSD / BOLD)'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 #
v2 contracts: solc 0.8.24+commit.e11b9ed9 confirmed from Etherscan (TroveManager, BorrowerOperations, Exact Match). TransientStorageClearingHelperCollision introduced 0.8.28 — does not affect 0.8.24. StorageWriteRemovalBeforeConditionalTermination fixed 0.8.17 — does not affect 0.8.24. No high-severity bugs in 0.8.24. v1 contracts: solc 0.6.11+commit.5ef660b1 confirmed from Etherscan (BorrowerOperations, LUSD token). All known high-severity Solidity bugs pre-date 0.6.x and were fixed before 0.6.11. Both versions clean.
Sources #
- Etherscanv1 BorrowerOperations Etherscan source verificationv1 BorrowerOperations: solc v0.6.11+commit.5ef660b1, Exact Matchretrieved 2026-05-16
- v2 TroveManager Etherscan source verificationv2 TroveManager: solc v0.8.24+commit.e11b9ed9, Cancun, Exact Matchretrieved 2026-05-16
- Official Solidity compiler known bugs listSolidity bugs.json — 0.8.24 and 0.6.11 have no active high-severity 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 →