★ Low-threshold multisig vs TVL
Veda (BoringVault)'s assessment for RD-F-028 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
[U18 RESOLVED — previously gray/protocol_opacity] Safe 0xD6E47E0F34ECc031E676254fd8b0E61b656a15a5 confirmed 3-of-5 (Safe Transaction Service mainnet API: threshold=3, owner_count=5). Five owner addresses confirmed. At $1.07B vault-infrastructure TVS with a zero-delay TimelockController (minDelay=0), a 3-of-5 threshold is below best-practice for this TVL tier (DeFi high-security posture typically requires 4-of-7 or higher with attested signer identities). Signer identities are not publicly disclosed — no ENS names or public team attribution for any of the 5 addresses. Not red because a genuine 5-owner Safe (not 1-of-2 or equivalent) provides non-trivial multisig protection requiring 3-signer coordination. Yellow reflects threshold adequacy gap relative to $1.07B TVL and the zero-delay execution pathway.
Sources #
- TxSafe Transaction Service mainnet — threshold=3 owner_count=5 confirmed (U18 primary evidence)Safe Transaction Service mainnet API (safe-transaction-mainnet.safe.global): Safe 0xD6E47E0F34ECc031E676254fd8b0E61b656a15a5 — threshold=3, owner_count=5, owners: [0xeC20A9462f7EdEc370AaD7c77bc999e054Ac4ba0, 0x6B3595C9A9262307075bA4a90EF6854a4802aC16, 0x162B522c4c8C4e246aebD23Ad236Da6831bB381a, 0x58a70365A6fD7A72172E2880Cb88CBcFcE2Db65d, 0x29d9dff059f3E321E1235ff74F3829Fa90D4eDd6]retrieved 2026-05-17
- Safe 0xD6E47E0F — overview and TimelockController linkSafe 0xD6E47E0F — SafeProxy 1.4.1, created Dec 18 2025, sole proposer/executor of TimelockController controlling $1.07B vault clusterretrieved 2026-05-17
Methodology #
Determine whether the multisig threshold is abnormally low relative to TVL peer cohort (e.g., 2-of-3 for a protocol with >$100M TVL where peer norm is 5-of-8).
See the full factor methodology and distribution across all protocols →