SSV Network
DAMASCUSStaking Infrastructure · Ethereum · $10B+ secured TVL · 10 contracts
Public risk assessment — scores are produced with the same methodology as monitored protocols
Security Profile
78
75
90
72
62
72
50
80
75
100
78
75
90
72
62
72
50
80
75
100
Audit History
Bug Bounty Program
Assessment
DVT is infrastructure-critical but niche. No oracle risk helps. Governance centralization and moderate maturity pull score down. Clean security track record.
Dimension Breakdown
How scores work →- Operator-cluster permissioning model with multi-party key shares
- Cluster registration and liquidation access controls
- Network fee recipient controlled by DAO multisig
- Validator exit requires operator consensus (threshold)
- SSV token fee model with operator-set pricing
- Liquidation mechanism for underfunded clusters
- Network fee creates minimum operational cost floor
- Economic model untested under extreme operator churn
- No external oracle dependency in core protocol
- Validator performance measured on-chain via consensus
- SSV token pricing not used in protocol logic
- Clean separation from price feed risks
- Mainnet since December 2023 (~29 months)
- No protocol exploit to date
- TVL moderate (~$2B in managed validators)
- Multiple audits (Least Authority, Quantstamp)
- Z-factor: 0.836
- DAO governance with SSV token voting
- Multisig execution for protocol changes
- Relatively low governance participation
- Protocol upgrades controlled by limited signers
- Maximum resilience under independent adversarial testing
- Comprehensive security coverage across all attack surfaces
- Active bounty program incentivizes continuous scrutiny
- No validated adversarial findings — score set to neutral baseline
- Active monitoring of operator performance
- Node runner infrastructure standards
- Incident response procedures not publicly documented
- Multi-client strategy for operator diversity
- DVT integrates with any staking protocol (Lido, RocketPool, etc.)
- Operator-level composition creates trust assumptions
- Key resharing and DKG add cryptographic composition surface
- Beacon chain dependency is well-scoped
- Member of 2 dependency cluster(s)
- No cross-protocol cascade exposure detected
- Score: 100/100 (higher = more isolated from systemic risk)
- Source: cross_protocol_composition.json dependency analysis
- OpenZeppelin base contracts
- Go-based SSV node client (separate supply chain)
- Solidity contracts are relatively minimal
- Off-chain DKG ceremony adds non-Solidity surface
Risk Drivers
Primary risk factors driving this score, ordered by severity.
Adversarial Risk Signals
Observable security posture indicators. These signals reflect publicly verifiable information and responsible disclosure outcomes. No specific vulnerability details are exposed.
Score History & Verification
Score provenance tracking begins with the next reassessment.
On-Chain Data
- Protocol Slug
- "ssv"
- Oracle
- BRORegistry (Base)
- Evidence
- IPFS (pinned)
- Staleness Threshold
- 24 hours
registry.getScore("ssv")Reduce exploitable risk
BlackHart Monitoring provides continuous adversarial analysis, vulnerability detection, remediation support, and verified reassessment when your risk posture improves.