Resolved-without-proof findings
Falcon Finance's assessment for RD-F-003 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Zellic medium finding 'StakedUSDf initialization may fail' acknowledged and fixed at commit 9c34a242. No public GitHub to verify the fix is in deployed bytecode. Pashov finding details not fully extractable from binary PDF. No unverifiable high/critical resolutions identified.
Detail #
Zellic found 1 medium finding: 'StakedUSDf initialization may fail' because vestingPeriod and cooldownDuration can be set to zero simultaneously. Acknowledgement and fix stated as commit 9c34a242ae6c39e2054d5e3bb62e44328339aaa1. Since there is no public GitHub, this fix cannot be independently verified against the deployed bytecode of the sUSDf implementation at 0x0D132bEE412E6619a4863AEEdad97541BfDa3F34. Pashov audit PDF is binary-encoded; the commit SHA referenced (9c34a242) appears in Pashov's scope targeting StakedUSDf.sol. No critical or high findings are identified as 'resolved without proof' because none were found at critical/high severity. Scored yellow for 1 medium unverifiable resolution due to closed-source constraint.
Sources #
- AuditPashov Falcon Finance Security Review PDFPashov audit PDF (binary); commit 9c34a242 referenced for StakedUSDf.sol scoperetrieved 2026-05-12
- Falcon Finance Zellic Audit — Medium FindingZellic medium finding: StakedUSDf initialization may fail; acknowledged and fixed in commit 9c34a242retrieved 2026-05-12
Methodology #
Count the number of findings the audit report marks "Resolved" or "Fixed" where no matching on-chain bytecode change or verifiable commit can be found.
See the full factor methodology and distribution across all protocols →