★ Post-audit code changes without re-audit
Ethena's assessment for RD-F-139 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
EthenaMinting V2 (0xe3490...) deployed approximately January 2024 per Etherscan; Pashov V2 audit dated May 2024 — approximately 4 months post-initial deploy creating an audit-lag window. Code4rena November 2024 invitational (0 high, 2 medium; mitigation review confirmed). Post-2024 OFT adapter deployments to 18 chains (Sep 2025+) lack confirmed audit coverage. Active commits through April 2026 on minting client repos — peripheral code uncertainty.
Sources #
- AuditCode4rena Nov 2024 invitational — 0 high, 2 medium; no constructor arg discrepancyhttps://code4rena.com/reports/2024-11-ethena-labsretrieved 2026-04-28
- Pashov V2 Audit 2024-05-23 — covers EthenaMinting V2 and StakedUSDeV2https://596495599-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsBsPyff5ft3inFy9jyjt%2Fuploads%2FJHbdthPqKCPoZFzrpryW%2Fv2-audit.pdfretrieved 2026-04-28
- OFT 18-chain deployment Sep 2025 — audit coverage for OFT adapters uncertainhttps://stabledash.com/news/2025-09-11-ethena-taps-layerzero-to-enable-one-click-usde-staking-across-18-blockchainsretrieved 2026-04-28
Methodology #
Count deployed changes to audited bytecode where no subsequent audit or spot-review covers the changed code.
See the full factor methodology and distribution across all protocols →