SSV Network

• Name: SSV Network
• URL: https://ssv.network/
• Category: Ethereum staking infrastructure / distributed validator technology / validator-coordination middleware
• Tags: ethereum-ecosystem
• Summary: SSV Network is DVT infrastructure packaged as an operator network rather than a single middleware client. The important cut is validator coordination and threshold signing across independent operators, not another staking front end. Keep this note on the validator network itself; use ssv-labs for the reference software and docs stewardship boundary, and ssv-foundation for the DAO-support and representation shell around governance.
• What it does:
  • Lets stakers distribute validator operations across clusters of independent operators instead of running a validator on a single machine
  • Splits validator signing keys into multiple encrypted key shares so no single operator holds the full validating key
  • Uses threshold signing and cluster consensus so validators can keep operating when part of the cluster is offline or faulty
  • Provides operator-node, staker, and developer documentation plus SDK and node software for integrating or running the network
  • Positions itself for staking services, custodians, exchanges, treasuries, and other operators that need Ethereum staking with stronger fault tolerance and separation of duties
• Key claims:
  • The official learn docs describe SSV Network as a decentralized, open-source ETH staking network built on Secret Shared Validator technology, where validator keys are split into key shares and distributed across multiple non-trusting nodes
  • The docs emphasize active-active redundancy, non-custodial validator operation, and client/operator diversity as core benefits relative to single-node staking setups
  • The security docs explain that validator clusters reach consensus on what to sign, aggregate threshold BLS signatures, and never reconstruct the validator private key during operations
  • The homepage frames the network as institutional-grade staking infrastructure for exchanges, custodians, and treasuries, with large-network adoption and a sizeable operator set
  • The public ssvlabs/ssv repository shows a real node implementation, operator setup path, audits, API docs, and an actively maintained technical surface beyond the marketing site
• Whitepaper: No single canonical SSV Network whitepaper was confirmed during this pass. The homepage references a “MICA Whitepaper,” but the clearest first-party sources for understanding the network in practice were the learn docs, security docs, and public node repository; see ../whitepapers/ssv-network-primary-sources-2026-04-26.md.
• Sources:
  • https://ssv.network/
  • https://docs.ssv.network/
  • https://docs.ssv.network/learn/introduction
  • https://docs.ssv.network/learn/security
  • https://github.com/ssvlabs/ssv
  • https://raw.githubusercontent.com/ssvlabs/ssv/main/README.md

Internal linkages

• Keep this anchor note on the strongest branch reads: obol and charon.
• Company and foundation boundaries that now deserve separate reads: ssv-labs and ssv-foundation.

Protocol / company / foundation boundary

• Keep projects/ssv-network on the validator network itself: operator clusters, key-share distribution, threshold signing, operator-market structure, and the staking-facing protocol surface.
• Use ssv-labs when the real question is who stewards the reference node, contracts, SDKs, docs, and public implementation path most builders and operators inherit.
• Use ssv-foundation when the real question is the DAO-support, representation, and protocol-assistance shell around governance rather than the software stack.
• That split matters because SSV’s practical authority is not one thing. The network, the implementation company, and the foundation / governance shell each answer different control-surface questions.

Control surface

• The inspectable protocol layer is validator registration, operator selection, fee setting, cluster topology, threshold-signing behavior, and the onchain contracts stakers and operators interact with.

• The harder offchain gravity sits in the reference software, docs, SDKs, and developer packaging now captured in ssv-labs, plus the governance-support and representation shell captured in ssv-foundation.

• Read SSV Network first as the distributed validator rail itself. Then split outward when the question becomes who stewards the software path? or which entity supports and represents the DAO layer?

• Last reviewed: 2026-08-10 UTC