Upgrade multisig signer configuration (M/N)
Across Protocol's assessment for RD-F-026 — scored gray on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Admin address count | 1 privileged multisig (`0xB524735356985D2f267FA010D681f061DfF03715`) holds all on-chain admin powers across HubPool, ConfigStore, and controls SpokePool upgrades via relaySpokePoolAdminFunction(). 5 undisclosed signers behind that Safe. ACX token owner is also a Safe (confirmed multisig; address not separately confirmed but stated by OZ head of security). Deployer `0x9a8f92a830` no longer holds admin roles (transferred at deploy). | Etherscan labels; profile §3; governan...
Sources #
- Curator noteExtracted from 02-governance-admin.md — RD-F-026; no URL citedretrieved 2026-04-28
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 →