Skip to main content

Quickstart

Please note

This page is for staking providers, pools, and similar services.

If you are an individual ETH holder, follow Solo-Stakers instead.

Stakers Diagram

SSV Network lets stakers run validators through distributed operators. Stakers fund validators and pay operator and network fees in ETH.

For more context, see SSV Network Overview and Security Overview.

How to integrate with SSV Network​

Overview​

At a high level, the process has four steps:

  1. Set up SSV nodes
  2. Register operators on SSV Network.
  3. Split validator keys.
  4. Register the generated key shares.

Prerequisites​

  • Infrastructure: Machines with synced execution-layer and consensus-layer clients.
  • Security: An offline or air-gapped environment for private key operations.
  • Access: Administrative access to your current validator setup, so you can shut it down during migration.
  • Wallet: An on-chain wallet with enough ETH for fees, collateral, and gas.
Testnet dry run

Before you use mainnet, run the full process on SSV testnet (Hoodi). This helps you validate your infrastructure, procedures, and key handling in a safer environment.

Step 1: Set up SSV nodes​

Deploy the SSV nodes that will operate your validators.

  1. Deploy SSV nodes

    Deploy one full setup per node. Supported cluster sizes are 4, 7, 10, and 13 operators.

    Recommended: SSV-Stack, quick setup. It will generate a random password and private key files on first start.
    Alternative: Manual setup.

  2. Configure monitoring

    Recommended: SSV-Stack includes Prometheus and Grafana. The default local address is http://localhost:3000. More details are in the SSV-Stack README.
    Alternative: For manual setups, deploy your own Grafana and Prometheus. Downnload our Grafana dashboard JSON.

  3. Configure MEV

    MEV settings are mainly handled on the consensus client. Follow our MEV boost setup guide.

Step 2: Register operators on SSV Network​

  1. Register each operator

    Follow Operator Registration once for each node you deployed. Use the public key derived from each node's private key files.

  2. Set operator details

  3. Back up operator secrets

    Back up the operator key files and password files.

    Critical

    Losing either file permanently disables that operator. If too many operators are offline, validators in the cluster will go offline, and you will have to repeat the migration process.

  4. Maintain the nodes

    Keep nodes updated with new SSV releases. If you run into issues, use the Troubleshooting guide.

Validator Onboarding​

Steps 3 and 4: follow the Validator Onboarding for key splitting and validator registration.