> For the complete documentation index, see [llms.txt](https://etherfi.gitbook.io/etherfi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://etherfi.gitbook.io/etherfi/~/changes/8Jd9g7SmBTNMrbOKtUZq/operation-solo-staker.md).
# Operation Solo Staker
Decentralizing Ethereum one node at a time!
Welcome to the documentation for Ether.fi's Operation Solo Staker, it's great to have you here 🥳
## What is Operation Solo Staker?
So you want to be part of the journey to decentralize Ethereum? This is the place to start!
Right now there are \~5,500 nodes running Ethereum, and about half are based in the US. Of these, over half are in a single data center in Virginia, 20 minutes away from the white house and the CIA headquarters. This is not a truly decentralized system. Ethereum needs Solo Operators!
Ether.fi
You
Provides the capital, hardware and software.
Provide the internet connection.
## So how does it work?
* Ether.fi has ETH that has been deposited by stakers.
* That ETH is then staked by Ether.fi to create Ethereum validators.
* For each 32 ETH deposited, one validator key is generated.
* These validator keys need to be given to node operators to perform validator duties such as proposing blocks and attesting (voting) to say that they are happy with the chain, etc.
* But if all those validator keys are given to a small number of existing node operators... it's not a truly decentralized system!
* That's where Operation Solo Staker comes in 💡
* Using DVT (more on that later) that single validator key can be split up and shared between multiple home stakers. This reduces operational risks and increases decentralization.
Or to put it simply...
Ether.fi provides the ETH, the machine, and the software. All you need is an internet connection. As long as your machine is online, it will support and validate the Ethereum network, and you will earn rewards!
## How can I get involved?
If you are looking to be involved in Operation Solo Staker, check out the link below for any updates
{% embed url="" %}
## I've been selected to be a solo staker! What do I need to do?
If you are part of the initial trial of 12 home stakers, congratulations! You're on your way to becoming a solo staker 🏠
The following documentation pages will outline what you need to know to get your machine set up, to import your validator keyshares (don't worry, that's explained next), and how to monitor and maintain your machine.
To start with, let's explain DVT, why we're using it and what you need to know:
{% content-ref url="/pages/KKeQ2HUbIcsRHZSmlkaG" %}
[Obol DVT Explained](/etherfi/~/changes/8Jd9g7SmBTNMrbOKtUZq/operation-solo-staker/obol-dvt-explained.md)
{% endcontent-ref %}
There are two machines being used in the initial trial, [Dappnode](https://dappnode.com/) and [Avado](https://ava.do/). Please follow the instructions for the specific machine you are using.
{% content-ref url="/pages/qwGL2MapsKv5ZPqChUBa" %}
[Avado Setup](/etherfi/~/changes/8Jd9g7SmBTNMrbOKtUZq/operation-solo-staker/avado-setup.md)
{% endcontent-ref %}
{% content-ref url="/pages/iInqBgrCqLB5qakqbglz" %}
[Dappnode Setup](/etherfi/~/changes/8Jd9g7SmBTNMrbOKtUZq/operation-solo-staker/dappnode-setup.md)
{% endcontent-ref %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://etherfi.gitbook.io/etherfi/~/changes/8Jd9g7SmBTNMrbOKtUZq/operation-solo-staker.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
