★ Sudden admin-rescue/ACL change without discussion
Pendle Finance's assessment for RD-F-123 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
No confirmed instance of a sudden admin-rescue or ACL change without preceding discussion found. The sPENDLE governance migration (largest recent change) was publicly announced via Medium post with community discussion. GitHub issues show open governance discussions (#44). However: (1) no governance forum exists (forum.pendle.finance 404), eliminating an archived pre-discussion trail for admin changes; (2) the Dev Multisig (2-of-5) operates without a timelock (data cache: timelock_address = null), enabling rapid ACL changes without buffer; (3) admin signer identities are not publicly labeled. Assessed yellow: structural gap exists but no confirmed undiscussed ACL-change event identified in the last 180 days.
Sources #
- InternalData cache — timelock_address null; governance forum absentData cache: timelock_address = null; forum.pendle.finance returns 404retrieved 2026-04-29
- pendle-core-v2-public issues — #44 Renovate Governance DashboardGitHub issues — governance discussion existsretrieved 2026-04-29
- Introducing sPENDLE | Pendle MediumsPENDLE introduction Medium post — major governance change with public discussionretrieved 2026-04-29
- Dev Multisig (0xE6F0) — 2-of-5, 5 owners | Safe APIDev Multisig Safe API — 2-of-5 threshold confirmedretrieved 2026-04-29
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 →