What Is SSV Network? Distributed Validators for Ethereum

A normal Ethereum validator runs on one machine with one key. If that machine goes offline, the validator misses rewards. If the key is copied to a second machine that runs at the same time, the validator can be slashed for signing twice. SSV addresses both problems ¹.

1. Key splitting. The validator key is generated, or created through distributed key generation (DKG), and split with Shamir secret sharing. Each operator holds one share. No share can sign on its own ².
2. Threshold signing. Clusters follow the rule n ≥ 3f+1. In a 4-operator cluster, one operator can fail and the validator still works. In a 7-operator cluster, two can fail ²⁴.
3. Consensus per duty. For every attestation or block proposal, the operators run an Istanbul BFT consensus round to agree on what to sign. They then combine their BLS partial signatures into one valid validator signature ².
4. Operators run SSV node software between their beacon node and validator client. Each operator chooses its own clients and hardware, which spreads client diversity ¹².

The result is a validator that can survive one or more operators going offline. Spreading a key across operators also lowers the risk that a single compromised machine leaks it ¹.

• Staking providers and pools that want to remove single points of failure. They run SSV nodes, register as operators and register their validators' key shares ⁴.
• Solo stakers, who can pick independent operators for their validator or run four or more SSV nodes themselves ⁵.
• Operators, who earn ETH fees for running validators. An operator can be public or "permissioned," meaning only whitelisted addresses can register validators with it ³¹⁴.

All of this runs through on-chain smart contracts and the SSV Web App, with a testnet on Hoodi for dry runs ⁴.

Running a validator on SSV has two recurring costs, both paid in ETH according to the current docs ⁶:

• Operator fees. Each operator sets its own fee, quoted per year per 32 ETH of effective balance and charged block by block. A cluster pays the combined fee of all its operators ⁶.
• Network fee. Set by the DAO at 1% of Ethereum's staking APR, per 32 ETH. It goes to the DAO treasury, and a share goes to SSV stakers ⁶⁹¹¹.

You prepay these fees into a cluster balance. The balance must stay above a "liquidation collateral" threshold: the larger of a fixed minimum and the cluster's fee rate over a set number of blocks. If it falls below, anyone can liquidate the cluster and collect the collateral as a reward. Operators then stop running the validators ⁷. A liquidated validator goes offline and starts losing rewards, so watching the cluster balance is part of using SSV. You can withdraw extra ETH from a cluster at any time, as long as you leave enough for fees and collateral ⁸.

Your staking rewards come from Ethereum itself, not from SSV. SSV adds costs on top of your normal validator setup (32 ETH per validator, gas and hardware if you self-operate). Separately, the DAO's Incentivized Mainnet Program has paid SSV token bonuses to validators on the network since October 2023, in tiers based on total network size ¹⁵.

SSV is the governance token of the SSV Network DAO. Holders vote on Snapshot proposals, and a governance multisig executes on-chain changes such as the network fee ¹¹. The docs give SSV two other jobs today ⁹¹⁰:

• Oracle staking. Holders stake SSV and receive cSSV, a transferable receipt. Their voting weight supports the oracles that report validators' effective balances on-chain. In return they earn a share of the ETH network fees. Unstaking has a 7-day cooldown.
• Legacy clusters. Older clusters that were set up to pay fees in SSV can still do so.

Earlier versions of the network charged fees in SSV. The move to ETH payments was audited by Quantstamp in March 2026 ¹².

• No single key holder. Operators only ever hold key shares. The docs recommend generating keys in an offline or air-gapped environment ¹⁴.
• Fault tolerance. Clusters keep working with up to f faulty operators, as described above ².
• Slashing is still possible if the same key runs outside SSV at the same time, for example a leftover copy on an old server. SSV's own post-mortem says its guarantees "no longer apply" in that case ¹⁸¹⁹.
• Audits. SSV publishes reports from 2023 through May 2026. They cover the protocol spec, node, contracts, DKG and oracle ¹². An audit lowers risk but does not rule out bugs.
• Bug bounty. Up to $250,000 per critical finding on Immunefi ¹³.

The core team, led by Alon Muroch, rolled out mainnet in stages during 2023, moving from permissioned operators to a permissionless network ¹⁶. The partner mainnet opened in September 2023. Fully permissionless registration for operators and validators followed on December 12, 2023 ¹⁷. The Incentivized Mainnet Program started in October 2023 ¹⁵. Later work added DKG resharing, bulk validator tools, the "Alan" peer-to-peer fork (2024) and, in 2026, ETH payments, SSV staking and on-chain effective-balance oracles ¹².