Upgrade multisig signer configuration (M/N)

Spiko'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 #

2-of-5 Safe at 0xEBB418e1f8E8F26BdF7816A2cD25bE87c040E425. Five owner addresses confirmed via Safe API. None publicly attested by name. required=2, total=5.

Sources #

URL
Spiko super-admin Safe API responseSafe API: threshold=2, owners=[0x6cA0aA6D3BF500d65F6e17a27aF05c74eD4BFb5A, 0xf949ca7be175a5FCbd3fEbb9A0235de608CA7898, 0x4896F23FF83242D8D4EB5fA1dEdF8c57e9145949, 0xA6e06dfE42064B7Cd6DC902a62e74ca5Bb574011, 0xe67D2cbeaE3090bE017C66e7A6943961619a5D35]retrieved 2026-05-16
Etherscan
Spiko Safe multisig on EtherscanEtherscan confirms GnosisSafeProxy 1.3.0 at 0xEBB418e1f8E8F26BdF7816A2cD25bE87c040E425, 169 transactionsretrieved 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 spiko factor RD-F-026 score yellow collected_at 2026-05-15 22:52:13