Use ssv.network validator infrastructure as a building block for any staking application.
Validator keys are distributed between multiple operators to provide fault tolerance, optimize performance, and minimize slashing risks.
To mitigate a single point of failure and malicious actors, your validator keys are kept offline, and no single operator has custody or access to them.
No operational setups are required. Network operators manage your pool’s validator nodes, allowing you to focus on building amazing staking applications.
Pick and choose between the network operators, and optimize for cost and tech stack (geo and client diversity).
Get funded to build the future of ETH staking. The ssv.network DAO has grants available for developers to build apps and tools using SSV infrastructure.
Learn how to build a DVT based Staking Pool Guide
To achieve true active – active fault tolerance SSV’s QBFT consensus mechanism can handle 1 malfunctioning node out of 4 nodes operating a single validator.
Consensus based duty validations eliminate potential slashing risks.
Distribute Infrastructure – distributing responsibility between nodes results in much lower operational risk.
Earn SSV fees by participating as a network operator for maintaining validators on behalf of stakers.
Learn how to build a DVT-based staking service
Withdrawal credentials are never shared and the validation key is kept offline – no single operator has custody or access to the validator keys.
Select and manage your preferred tech stack for your validators (geographic and client diversity).
Validators’ keys are distributed between multiple operators to enable fault tolerances, optimized performance, and minimized slashing risks.
Run your validator on the robust infrastructure of the most experienced and reputable node operators in the staking industry.
SSV boasts many operators with unique client configurations, enabling total control over execution and consensus client choice.
SSV has over $100M TVL operated through EigenPods and Restaking Protocols.
Each operator in the cluster maintains a slashing database to prevent a slashable duty from ever being submitted.
Run your validators in unique geographical locations with minority clients.
