> 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/archive/solo-stakers.md).

# Solo Stakers (Archived)

Archived — the ether.fi solo staker program is no longer active. Kept for historical reference.

{% hint style="warning" %}
**This section is archived.** The ether.fi solo staker program is no longer active, and these guides are kept for historical reference — they may be out of date. To run validators with ether.fi today, see [Node Operators](/etherfi/archive/node-operators.md).
{% endhint %}

Solo stakers run Ethereum validators that secure the ether.fi network. Through **distributed validator technology (DVT)** — powered by Obol and SSV — you can operate a validator with improved fault tolerance and without trusting a single machine. This section walks you through onboarding, hardware, setup with Avado or Dappnode, and validator lifecycle management.

New operator? Begin with onboarding, then pick the setup path that matches your hardware.

## Get set up

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>🥩 Operation Solo Staker</strong></td><td>Onboarding plus full Obol and SSV setup guides (Avado, Dappnode, and custom).</td><td><a href="/etherfi/archive/solo-stakers/operation-solo-staker.md">Operation Solo Staker</a></td></tr><tr><td><strong>👋 Solo Staker Onboarding</strong></td><td>Start here — what you need and how to join the network.</td><td><a href="/etherfi/archive/solo-stakers/operation-solo-staker/solo-staker-onboarding.md">Solo Staker Onboarding</a></td></tr><tr><td><strong>🔗 Solo Staking Hardware</strong></td><td>Recommended hardware to run a reliable validator.</td><td><a href="/etherfi/archive/solo-stakers/solo-staking-hardware.md">Solo Staking Hardware</a></td></tr><tr><td><strong>🚪 Validator Exits</strong></td><td>How to exit a validator and what to expect.</td><td><a href="/etherfi/archive/solo-stakers/validator-exits.md">Validator Exits</a></td></tr></tbody></table>

{% hint style="info" %}
Running validators at scale as a professional operator? See the [Node Operators](/etherfi/archive/node-operators.md) section instead.
{% endhint %}


---

# 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/archive/solo-stakers.md?ask=<question>&goal=<user_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.