Dependency tree uses EOL Solidity version
Falcon Finance's assessment for RD-F-174 — scored green on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Solidity 0.8.28 and 0.8.30 are within the actively maintained 0.8.x series. Latest release 0.8.34 (Feb 2026). Not EOL. No Vyper detected.
Detail #
Core contracts use v0.8.28 (released Oct 2024). Post-TGE contracts use v0.8.30 (released May 2025). Latest Solidity release is 0.8.34 (Feb 2026). Both 0.8.28 and 0.8.30 are within the actively maintained 0.8.x series — Solidity has not announced an EOL policy for these versions. The fact that 0.8.34 exists as a patch release does not make 0.8.28/0.8.30 'EOL.' No Vyper detected (data cache: vyper_detected: false). The SOL-2026-1 bug in 0.8.28-0.8.33 is addressed in F170, not here.
Sources #
- URLSolidity 0.8.34 Release AnnouncementSolidity 0.8.34 release Feb 2026 — 0.8.28/0.8.30 still in active seriesretrieved 2026-05-12
- USDf Implementation — EtherscanUSDf impl: Solidity v0.8.28 (not EOL); sFF: v0.8.30 (not EOL)retrieved 2026-05-12
Methodology #
Determine whether the deployed code or its dependencies use an EOL or unsupported Solidity version without a forward-compatibility patch.
See the full factor methodology and distribution across all protocols →