Upgrades can be executed in 0 seconds. Several paths can bypass the standard governance process.
The control setup leaves users and monitoring systems very little (or no) time to react if something goes wrong.
0 seconds. No enforced delay before an upgrade takes effect.
The main control-plane risks found in this scan, with plain-English impact and remediation.
Meaning: Upgrades can be executed immediately. There is no enforced waiting period between an upgrade being proposed and it taking effect on-chain.
Fix: Enforce a meaningful timelock delay (e.g. 24–72 hours) on every upgrade path so users and monitoring systems have time to react.
Meaning: 3 upgrade routes may avoid the expected governance process.
Fix: Audit each alternative path. Remove direct upgrade permissions and ensure every route enforces the same delay and approval requirements.
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.
A concrete sequence of how this risk could play out. This is illustrative, not a prediction.
This is not a detected exploit. It illustrates the control failure this configuration may allow.
6 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.
Upgrade paths that may bypass the expected governance or timelock delay.
Wallet 0x3437…0e78 can upgrade with zero delay
This path appears to bypass the expected governance delay. If the wallet is compromised or misused, the implementation can be changed immediately.
Remove direct wallet upgrade authority or place it behind the same multisig and timelock as the standard upgrade route.
Wallet 0x8EbB…eABc can upgrade with zero delay
This path appears to bypass the expected governance delay. If the wallet is compromised or misused, the implementation can be changed immediately.
Remove direct wallet upgrade authority or place it behind the same multisig and timelock as the standard upgrade route.
4 distinct upgrade paths with delays: 2.0d, 0s
If this path is used, the protocol implementation may be changed faster than the normal governance process allows.
Audit this path. Either remove the permission, or place it behind the same multisig and timelock as the standard upgrade route.
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 50 events.
Get a control-plane scan showing who can upgrade your contracts, how fast, and through which paths. Find direct upgrade paths, missing delays, and governance bypasses before they become incident response problems.
Includes authority graph, bypass paths, effective delay, and upgrade history.