★ Audit scope mismatch
EigenLayer's assessment for RD-F-001 — scored green on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
22 audit engagements across ConsenSys Diligence, Sigma Prime, Cantina, and Certora track deployed code from M1 (2023) through Rewards v2.2 (Feb 2026). Cantina competition commit 722f3cbeb7721431f1a2a4a73582f7981212e23d and Sigma Prime PR #679 provide commit-level anchoring for slashing release. One narrow uncertainty: the August 2025 EigenPods Pectra hotfix (v1.6.1) executed via community multisig may lack a dedicated post-fix external audit. Overall scope coverage across lifecycle is strong.
Sources #
- GitHubSigma Prime EigenLayer Slashing Security Assessmentsigp/public-audits — EigenLayer slashing v2_0 PDFretrieved 2026-04-28
- EigenLayer public audits directoryLayr-Labs/eigenlayer-contracts/tree/main/auditsretrieved 2026-04-28
- Cantina EigenLayer V1.3.0 Slashing CompetitionCantina EigenLayer slashing competition — commit 722f3cbeb7721431f1a2a4a73582f7981212e23dretrieved 2026-04-28
- EigenPods Bug Fix Completed - August 29 2025EigenPods bug fix August 29 2025 — forum post describing v1.6.1 emergency patchretrieved 2026-04-28
Methodology #
Check whether the commit SHA cited in the audit report matches the bytecode deployed at the production proxy/implementation address.
See the full factor methodology and distribution across all protocols →