Prior to running a validator on the SSV network you must have a deposited validator on the Beacon Chain.
Both pending and active validators are supported - if you have just made a deposit to your validator, you can register your validator to our network while it's pending on the queue, and once it gets activated, your selected operators will operate it immediately.

Generate a validator key

In order for the SSV operators to operate your validator, you must supply your chosen cluster of operators with your validator’s private key.
If you do not have a validator key, you can create one via Ethereum launchpad.
Please note - you remain in full custody of your validator as you keep the withdrawal key to yourself. only the private key is required, which is never stored or sent to our servers in any way and is distributed to your operators via encrypted keyshares. As each operator in the cluster receives a single keyshare, they can never reconstruct or access your validator key on their own.

Deposit your validator

You must have an active validator before running it on the SSV network.
In order to have an active validator on the Beacon Chain, you need to deposit 32 ETH per each validator that you wish to run by making a transaction to the deposit contract.
If you have not made a deposit for your validator, you can do so via Ethereum launchpad.
If you prefer to do this on your on, make sure to verify the deposit address beforehand at

Slashing warning

Running a validator simultaneously to the SSV network will cause slashing to your validator.
If you have an existing validator setup, please shut it down before running your validator on our network to avoid slashing.
Please note - it’s best practice to wait at least 2 epochs without attending duties before setting up your SSV validator.