★ Sudden admin-rescue/ACL change without discussion
Euler V2's assessment for RD-F-123 — scored green on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
No non-routine admin-rescue or ACL change found without corresponding governance discussion in the past 180 days (Nov 2024 – May 2026). The Euler v2 per-vault governor model routes parameter changes through documented eIP process: forum RFC → Snapshot vote → on-chain execution. 'Prepare EVK Factory for Pause Guardians' RFC (Sept 17 2024) was posted publicly before implementation (posted by 'doug' = Doug Hoyte; 0 replies but publicly disclosed). eIP 62 (Feb 25 2025, 'Optimistic Risk Management: timelocked risk stewards and limited rapid response') addresses the ACL/governor change process directly. Emergency guardian roles (Euler Labs, Gauntlet) are documented in governance architecture, not hidden. No undiscussed admin-rescue event identified.
Sources #
- URLEuler Governance Forum — Protocol categoryEuler Governance Forum — RFC: Prepare EVK Factory for Pause Guardians (Sept 17 2024, posted by doug)retrieved 2026-05-04
- Euler Governance Forum — eIP 62eIP 62: Optimistic Risk Management (Feb 25 2025) — timelocked risk stewards governanceretrieved 2026-05-04
Methodology #
Determine whether any admin-rescue function or ACL change was committed to the repo or executed on-chain without corresponding public discussion in issues, PRs, or governance forum.
See the full factor methodology and distribution across all protocols →