Auditor re-engaged after last exploit

Evidence summary #

For rsETH/Kelp: root cause was external (Kelp's LayerZero DVN config). No Aave contract vulnerability was found. No specific post-incident targeted audit of Aave's collateral onboarding or LRT acceptance criteria announced. Certora continuous FV and multi-firm audit cadence provide ongoing coverage but no explicit post-incident re-engagement. Yellow: ongoing auditor engagement present but no specific incident-triggered re-audit announced.

Sources #

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 →