Auditor re-engaged after last exploit
Fluid's assessment for RD-F-083 — scored gray on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
No evidence of auditor re-engagement specifically in response to the March 2025 Resolv/USR contagion incident. December 2025 security budget request (gov.fluid.io/t/security-budget-request/1754) references ongoing Certora formal verification — predates the incident and represents general security investment. The incident root cause was oracle configuration, not Fluid smart contract code vulnerability, making a targeted code re-audit ambiguous. Cannot assess whether a re-audit occurred; gray on insufficient evidence.
Sources #
- GovernanceFluid Governance — Security Budget Request December 2025gov.fluid.io/t/security-budget-request/1754 — December 2025 security budget; references ongoing Certora FV, 20+ audits; no post-incident re-audit announcementretrieved 2026-04-29
Methodology #
Determine whether a reputable auditor performed a re-audit or incident review after the most recent exploit.
See the full factor methodology and distribution across all protocols →