★ Sudden admin-rescue/ACL change without discussion
Lista DAO'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 #
[★ CRITICAL FACTOR] Profile §11 identifies 3 transactions on April 8, 2025 on the Lending TimeLock: two GRANT_ROLE and one REVOKE_ROLE from creator address 0xd7e38800.... GitHub issues list for lista-dao-contracts returned empty (no issues at all, not selective absence). No Snapshot proposal or public community discussion corresponding to these April 8, 2025 role grants was located. Scoring yellow (not red) because: (a) the transactions appear to be TimeLock initialization/setup (granting PROPOSER_ROLE + EXECUTOR_ROLE to multisig, revoking deployer's admin role), not an emergency admin-rescue of live-TVL contracts; (b) the protocol's apparent practice of zero GitHub issues means absence of discussion is structural, not targeted suppression; (c) the change is consistent with normal TimeLock deployment pattern. If any subsequent post-deploy ACL change on live-TVL contracts occurs without Snapshot or public discussion, this factor should flip to red.
Sources #
- Governancelistavote.eth Snapshot spaceSnapshot space listavote.eth — no proposal corresponding to April 2025 TimeLock role-grant transactions identifiedretrieved 2026-05-12
- BSCScan: Lending TimeLockBSCScan: Lending TimeLock 0x2e2807F88... created ~April 2025 by 0xd7e38800...; profile §11 notes 3 role-grant transactions on April 8, 2025retrieved 2026-05-12
- lista-dao-contracts GitHub Issues (empty)GitHub issues list for lista-dao-contracts returned no results — no admin-change discussion threads existretrieved 2026-05-12
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 →