★ Sudden admin-rescue/ACL change without discussion
Liquid Collective (LsETH)'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 evidence of clandestine admin-rescue or ACL changes. All major upgrades (v1.0.0 through v1.3.0) are accompanied by GitHub release notes with linked PRs. Issue #447 (May 4, 2026) flags 'missing admin access control in initialization function' preceding Pectra upgrade — showing pre-upgrade discussion. Issue #84 (Aug 2022) addresses single-step ownership change governance. However, consortium governance is off-chain among Safe signers with no public governance forum — the 36 Proxy Admin Safe execution transactions cannot be individually matched to public discussion threads. This creates transparency opacity but no evidence of malicious undisclosed changes. Yellow: upgrades GitHub-tracked and pre-discussed; Safe-level execution discussion is opaque due to absent public forum.
Sources #
- GitHubReleases - liquid-collective-protocolGitHub releases — v1.0.0 through v1.3.0 each with linked PRsretrieved 2026-05-17
- Liquid Collective: Proxy Admin Safe - EtherscanProxy Admin Safe — 36 exec transactions, last Oct 22 2025; no public forum matching Safe executionsretrieved 2026-05-17
- Pectra Phase 1 missing admin access control in initialization functionGitHub Issue #447 — missing admin access control in initialization function (May 4, 2026, open before Pectra upgrade)retrieved 2026-05-17
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 →