No upgrade mechanism was found. The contract code on-chain today is the code forever; no one can change it.
You do not need to trust any operator to refrain from changing the protocol. The risk surface is limited to the original code.
Not applicable. The contract cannot be upgraded at all.
The main control-plane risks found in this scan, with plain-English impact and remediation.
Meaning: No mechanism exists to change the contract code after deployment.
Fix: No action needed. The risk surface is limited to the original code.
All 1 recommended fix apply to this protocol.
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.
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.