DVT Relayer is a service providing validators' registration data to Stakewise v3-operator in DVT setup.
As a general introduction in DVT read the article on Ethereum web-site. For technical details see Obol docs or SSV docs.
Distributed validator (DV) keystores are used:
- on DVT sidecars
- for Relayer testing
The easiest way to generate DV keys for testing is Obol launchpad. Works for Hoodi, Mainnet and Gnosis. Select appropriate network. Then select "Create a distributed validator alone". Follow instructions. Use vault address as withdrawal address.
In production environment:
- Validators' keystores should be created via distributed key generation (DKG) procedure
- DVT Relayer should not have access to DV keystores.
- Install poetry
- Install dependencies:
poetry install
cp .env.example .env
- Fill .env file with appropriate values
poetry shell
export PYTHONPATH=.
python src/app.py
Running the whole cluster of DVT sidecars locally may be cumbersome. For testing purpose single sidecar may work on behalf of several DVT operators. See DVT sidecar readme for details.
DVT sidecar:
- Loads DV keystores
- Polls validator exits from Relayer
- Pushes exit signature shares to Relayer on behalf of DVT operators.