Upgrade multisig signer configuration (M/N)

Circle USYC's assessment for RD-F-026 — scored red on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.

Evidence summary #

No multisig identified for any role. Both upgrade-executing addresses are EOAs. Display: 1/1 (EOA). Data cache safe_multisigs: []. Profile confirms no Safe multisig exists (honest-null).

Sources #

Etherscan
Upgrade executor EOA - Etherscan0x13FF8Cabb86eDf94a2dF4f98773bda4005182dD6 - EOA, 2 total transactions, no contract coderetrieved 2026-05-16
Internal
00-data-cache.json and 00-profile.md section 6Data cache safe_multisigs: [], profile section 6 Admin multisig: None foundretrieved 2026-05-16

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 →

rubric_version v1.7.0 protocol circle-usyc factor RD-F-026 score red collected_at 2026-05-15 21:56:43