Validator

We need create validator keys with our forked version of Ethereum Staking Deposit cli, then run your validators manually or with SSV.

Run validator manually

Please configure the fee recipient as the FeePool contract. You can find the FeePool contract address through Factory contract. For example:

Option 1. Prysm

Details about the configuration of Prysm, you can check here.

It may take hours or days for your validator to become fully activated. To learn more about the validator activation process, see Deposit Process. See Check node and validator status for detailed status monitoring guidance. In the meantime, leave your execution client, beacon node, and validator client terminal windows open and running; once your validator is activated, it will automatically begin proposing and validating blocks.

To check on the status of your validator, we recommend checking out the popular block explorers: beaconcha.in by Bitfly and beaconscan.com by the Etherscan team.

Note:
Please configure the fee recipient as the FeePool contract, otherwise you may be slashed.

Next:
⚠️You MUST run ejector service, otherwise you may be slashed.
Follow our ejector doc to run ejector service for the validator.

Option 2. SSV

ssv.network is a fully decentralized, open-source ETH staking network, based on Secret Shared Validator (SSV) technology, which enables the distributed operation of an Ethereum validator. The SSV protocol splits a validator key into multiple KeyShares and distributes them to non-trusting nodes run by operators. The nodes execute the validator’s duties under a consensus mechanism providing fault tolerance, increased security, and decentralized risk for stakers.

More details on SSV portal: https://ssv.network/

Note:
Please configure the fee recipient as the FeePool contract, otherwise you may be slashed.

Next:
⚠️You MUST run ejector service, otherwise you may be slashed.
Follow our ejector doc to run ejector service for the validator.

Run validator by SSV client for trust validator

ssv.network is a fully decentralized, open-source ETH staking network, based on Secret Shared Validator (SSV) technology, which enables the distributed operation of an Ethereum validator. The SSV protocol splits a validator key into multiple KeyShares and distributes them to non-trusting nodes run by operators. The nodes execute the validator’s duties under a consensus mechanism providing fault tolerance, increased security, and decentralized risk for stakers.

SSV Client

• Listen to whether there is enough ETH in the user pool. If so, automatically generate a new validator key, signature, deposit data, etc., based on the mnemonic, and interact with the node contract to stake ETH and become a validator.

• Monitor SSV-related events and calculate the cluster’s latest state.

• Based on the configured operator, along with the validator key from step 1 and the cluster state from step 2, generate parameters such as signature, pubkeys, keyshare, etc., using SSV’s related algorithms, and interact with the SSV contract to trigger RegisterValidator.

• Monitor the validator’s status. If it exits, interact with the SSV contract to trigger RemoveValidator.

• Monitor the operator’s status. If a switch is required, interact with the SSV contract to trigger RemoveValidator/RegisterValidator to switch to new operators.

• Monitor the cluster balance. If it approaches the liquidation value, interact with the SSV contract to trigger Deposit to avoid liquidation. If it has already been liquidated, trigger Reactivate to recover the cluster.

• Monitor the validator Ejected status. If an eject is needed, trigger ExitValidator on the beacon.

• Listen to whether there is enough ETH in the user pool. If so, automatically generate a new validator key, signature, deposit data, etc., based on the mnemonic, and interact with the node contract to stake ETH and become a validator.

• Monitor SSV-related events and calculate the cluster’s latest state.

• Based on the configured operator, along with the validator key from step 1 and the cluster state from step 2, generate parameters such as signature, pubkeys, keyshare, etc., using SSV’s related algorithms, and interact with the SSV contract to trigger RegisterValidator.

• Monitor the validator’s status. If it exits, interact with the SSV contract to trigger RemoveValidator.

• Monitor the operator’s status. If a switch is required, interact with the SSV contract to trigger RemoveValidator/RegisterValidator to switch to new operators.

• Monitor the cluster balance. If it approaches the liquidation value, interact with the SSV contract to trigger Deposit to avoid liquidation. If it has already been liquidated, trigger Reactivate to recover the cluster.

• Monitor the validator Ejected status. If an eject is needed, trigger ExitValidator on the beacon.

Install Build Tools

Install make, gcc and git

sudo apt update
sudo apt install -y make gcc git build-essential

Install go by following the official docs. Remember to set your $PATH environment variable, for example:

cd $HOME
wget -O go1.21.6.linux-amd64.tar.gz https://go.dev/dl/go1.21.6.linux-amd64.tar.gz
rm -rf /usr/local/go && tar -C /usr/local -xzf go1.21.6.linux-amd64.tar.gz && rm go1.21.6.linux-amd64.tar.gz
echo 'export GOROOT=/usr/local/go' >> $HOME/.bashrc
echo 'export GOPATH=$HOME/go' >> $HOME/.bashrc
echo 'export GO111MODULE=on' >> $HOME/.bashrc
echo 'export PATH=$PATH:/usr/local/go/bin:$HOME/go/bin' >> $HOME/.bashrc && . $HOME/.bashrc
go version

Install SSV Client service

git clone https://github.com/stafiprotocol/eth-lsd-ssv.git
cd eth-lsd-ssv
make install

Import trust node account

$ lsd-ssv-client import-account
keystore path: ./keys
Enter private key:
>
password for key:
>
INFO[0007] key imported                                  address=0x68146ebA486CE6F8D22731c8ECB4d013F34E7114 file=CWD/keys/0x68146ebA486CE6F8D22731c8ECB4d013F34E7114.key

Import your SSV account

$ lsd-ssv-client import-account
keystore path: ./keys
Enter private key:
>
password for key:
>
INFO[0007] key imported                                  address=0x68146ebA486CE6F8D22731c8ECB4d013F34E7114 file=CWD/keys/0x68146ebA486CE6F8D22731c8ECB4d013F34E7114.key

Import validator mnemonic for creating new validators

$ lsd-ssv-client import-val-mnemonic

Config eth lsd ssv client service

Update config (config.toml) by your favorite editor

$ cp conf.ssv.template.toml config.toml

contracts section

Start ssv services

$ lsd-ssv-client start --config config.toml