Upgrade multisig signer configuration (M/N)
Axelar Network's assessment for RD-F-026 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Gateway upgrades require Cosmos governance (≥2/3 validator quorum by quadratic-weighted stake) relayed through InterchainGovernance. Operator role: custom Multisig 3-of-6 (threshold=3, owners=6). ITS upgrades: single bare EOA (0x6f24...) directly calls upgrade() — no multisig. Two-tier architecture: strong on gateway, absent on ITS surface. Not a Gnosis Safe for any surface.
Sources #
- EtherscanITS upgrade tx Jul 9 2025 — EtherscanITS upgrade tx Jul 2025: FROM=0x6f24A47Fc8AE5441Eb47EFfC3665e70e69Ac3F05 (bare EOA), direct upgrade() callretrieved 2026-05-17
- Custom Multisig (3-of-6) — EtherscanCustom Multisig 0xCC940AE49C78F20E3F13F3cF37e996b98Ac3EC68 readContract: threshold=3, 6 ownersretrieved 2026-05-17
Methodology #
Read `threshold` and `getOwners()` on the multisig controlling upgrade / sensitive ops. Store as `required` (M) and `total` (N); render as "M/N". For EOA admins record `required=1, total=1` (display "1/1"). Null when admin is immutable or full DAO with no fixed signer set.
See the full factor methodology and distribution across all protocols →