Upgrade multisig signer configuration (M/N)
OpenEden'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 #
4-of-5 threshold on Safe 0x8Ec4dD2DF01c188Ac5a5D870029E9cbb820d5844. Five owners: 0x39736Ba27Dae1dc551EF1593ccF53f57798eF424, 0x40214aE3c737Cc61088b087e15A41FfCDBd5Ad05, 0x2e8aBe537b0e8fc57F5D7d319Ce315c5fB91fAc0, 0x818566E881e762BEaC64dc32F81Ffc380680251a, 0xBdADa500EF197Dde58A6EFb5DC8EC84989E4c2c8. None publicly attested by name. Nonce=142 (active Safe). Yellow for signer identity opacity.
Sources #
- URLGnosis Safe API response — OpenEden admin SafeSafe Transaction Service API — threshold=4, owners=5, nonce=142, masterCopy=0xd9Db270cretrieved 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 →