Resolved-without-proof findings
Morpho V1 (Morpho Blue + MetaMorpho)'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 #
No known evidence of findings marked resolved without on-chain proof; release tag progression (alpha->beta->v1.0.0) indicates iterative fix application; full PDF review not completed due to binary PDF access limitations.
Detail #
The three-tag progression (v1.0.0-alpha following Spearbit review, v1.0.0-beta for Cantina competition, v1.0.0 for Cantina competition fixes) indicates that audit findings were worked through iteratively before mainnet launch. Morpho Blue's immutability means post-deploy 'unresolved' findings cannot be silently unfixed via a future upgrade — they would require a full redeployment. No post-mortem or incident reveals an ignored pre-launch finding. However, the audit PDFs could not be read directly (binary rendering failure in available tools), so finding-level resolution verification was not completed. Yellow reflects this evidence gap rather than an adverse finding.
Sources #
- GitHubhttps://github.com/morpho-org/morpho-blue/releasesretrieved 2026-04-27
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 →