★ Sudden admin-rescue/ACL change without discussion
Lombard 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 #
Deployer EOA `0x3F6Bf1c36Ccbb59eAf8415301a0Cec73C344A079` retains Proposer role in LombardTimeLock `0x055E84e7FE8955E2781010B866f10Ef6E1E77e59` alongside the 3-of-5 GnosisSafe — creating a single-actor upgrade path with only 1-hour timelock delay. No public governance forum (Snapshot, Discourse, Tally) identified for Lombard. April 2026 GitHub commits include ACL role revocations ('Revoke CALLER_ROLE,' 'Remove deprecated OPERATOR_ROLE references') consistent with OpenZeppelin and Sherlock April 2026 audit findings, but no pre-execution public discussion venue exists to verify. No hostile admin-rescue event documented. Yellow: structural concentration + no public ACL-change discussion forum; not a confirmed malicious event.
Sources #
- Etherscanhttps://etherscan.io/address/0x055E84e7FE8955E2781010B866f10Ef6E1E77e59retrieved 2026-05-05
- https://github.com/lombard-finance/evm-smart-contracts/commits/mainretrieved 2026-05-05
- https://docs.lombard.finance/governance/the-liquid-bitcoin-foundationretrieved 2026-05-05
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 →