Upgrades require timelock contract and wait 3 minutes before taking effect.
The control setup looks healthy. Users and monitoring systems have meaningful time to react before any upgrade goes live.
3 minutes. Users have time to monitor and respond.
The main control-plane risks found in this scan, with plain-English impact and remediation.
Meaning: The protocol logic can be replaced after deployment. This is common, but it makes the safety of the upgrade process critical.
Fix: Document the upgrade process publicly and monitor implementation changes in real time.
Meaning: Frequent upgrades increase dependency on the safety of the upgrade process.
Fix: Maintain a public changelog and monitor implementation changes in real time.
5 of 7 recommended fixes still apply to this protocol.
Architectural changes that close the most direct risk paths.
Process and monitoring practices that reduce ongoing risk.
The on-chain data behind the findings above. Switch to Advanced to see raw addresses, blocks, and method-level detail.
Who can change the protocol and through which path.
Recorded implementation or admin changes detected on-chain.
Per-event detail (block numbers, sender addresses, code addresses) is hidden in Simple view. Switch to Advanced to see all 6 events.
See exactly who controls upgrades, how long users have to react, and whether any path can bypass governance, for any protocol you operate or depend on.
Includes authority graph, bypass paths, effective delay, and upgrade history.