Upgrade multisig signer configuration (M/N)
SUNSwap (sun.io)'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 #
No multisig of any kind confirmed for AMM factories or V4 admin path. TRON has no Gnosis Safe deployment. safe_multisigs: [] in data cache. Deployer addresses confirmed as single EOA accounts (accountType:0 via tronscanapi). TRON-native multisig-equivalent not available through standard pipeline tooling.
Sources #
- URLTronScan API — V4 deployer account type EOAtronscanapi.com EOA confirmation TU3rMHyWHzeEJBReWLzHko728hbz6MtfNg accountType:0retrieved 2026-05-17
- SUNSwap data cache — safe_multisigs empty00-data-cache.json safe_multisigs: []retrieved 2026-05-17
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 →