Upgrade multisig signer configuration (M/N)
Falcon Finance'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-6 threshold (Safe API confirmed). 6 owner addresses; threshold=4. At $1.618B TVL, 4/6 is below peer norm of 5/8+ for billion-dollar protocols with no timelock.
Detail #
Safe API response: threshold=4, owners=[0x804016c31e52805eb00e0Ef42126Fd3e980A0b33, 0xF4161ed9CFa2ac91068556387F9ce225fCe6893f, 0xE313dbD8693d656Fe760Ba3E766C80eB08F06734, 0xA91472aCc85272fd4119a946796Aaf6c8392b0C0, 0x276c580545293dA6c7c0FDD12038Cc75acCBd211, 0xa76095b4a145055c3cc46ED64dd1bCF8a8544e6C]. One of 6 is labeled 'Falcon Finance: Deployer'. Other 5 are unattested pseudonymous addresses.
Sources #
- URLSafe Transaction Service — Falcon Finance Admin Safehttps://api.safe.global/tx-service/eth/api/v1/safes/0x1E482B60bf19Cb1cc859389e0eA3DED153f16Bd7/retrieved 2026-05-12
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 →