centralization-risk

Centralization risk in Sui Move packages stems from mismanaged privileged capabilities and governance controls that create single points of failure or unauthorized access. It involves analyzing AdminCap, UpgradeCap, and TreasuryCap ownership to ensure protocol security.

To mitigate centralization risk during a Sui security audit, analyze privilege capabilities like AdminCap and UpgradeCap, evaluate their ownership and transferability, identify single points of failure, and establish emergency power recovery plans.

You should check AdminCap, OwnerCap, UpgradeCap, and TreasuryCap for centralization risk. This involves analyzing capability ownership, transferability, destruction risks, and governance dependencies across upgrade, administration, and treasury functions.

Mapping capability hierarchy in Sui requires inventorying all privileged objects and classifying their ownership, transferability, and destruction risks based on store, drop, and init versus runtime properties to identify governance dependencies.

You need to analyze emergency power recovery in Sui protocols during security audits when evaluating centralization risk, ensuring that recovery plans exist for privileged capability controls across administration, upgrades, and treasury functions.