> 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/node-operators.md).

# Node Operators (Archived)

Professional operators who bid on, win, and run ether.fi validator nodes.

Node operators are partners who run ether.fi validator nodes at scale. This section helps you connect to the web application, bid on the right to run ether.fi nodes, receive keys when you win auctions, and decrypt and import those keys into your own infrastructure.

## Operator guides

<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>Dapp walkthrough</strong></td><td>Connect to the web application and navigate the operator flow.</td><td><a href="/etherfi/archive/node-operators/dapp-walkthrough.md">Dapp walkthrough</a></td></tr><tr><td><strong>Node operators guide</strong></td><td>Bid on auctions, receive keys, and run nodes end to end.</td><td><a href="/etherfi/archive/node-operators/node-operators-guide.md">Node operators guide</a></td></tr><tr><td><strong>Relayer</strong></td><td>How the relayer fits into the operator workflow.</td><td><a href="/etherfi/archive/node-operators/relayer.md">Relayer</a></td></tr></tbody></table>

{% hint style="info" %}
Running a single validator from home? See the [Solo Stakers](/etherfi/archive/solo-stakers.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 dynamically 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/node-operators.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 `build a script that syncs our docs to a CMS` 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.