> For the complete documentation index, see [llms.txt](https://docs.energyweb.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.energyweb.org/ewc-validator-documentation/start-here/ewc-validator-documentation-overview.md).

# EWC Validator Documentation Overview

Welcome to the homepage for Energy Web Chain validator technical documentation! 

This space is organized into two primary groups:

* [Installing a validator node](/ewc-validator-documentation/guides/installing-a-validator-node.md): Start here if you are new to the EWC validator community and setting up a node for the first time. 
* [Maintaining a validator node](/ewc-validator-documentation/guides/maintaining-a-validator-node.md): Here you will find step-by-step instructions for a variety of operational and maintenance tasks. 

If you need further information or troubleshooting assistance, please use the dedicated [Validator Knowledge Base](https://discuss.energyweb.org/c/knowledge-base/15). 

{% hint style="info" %}
**Note:** Validators can[^1] opt to outsource their node installation and operation to third-party service providers. 

Validators who opt to install and run their nodes externally can use [**Launchpad by Energy Web**](https://launchpad.energyweb.org/login) to install and host their Validator Nodes. Find detailed instructions in our [Quick Start Guide](https://docs-launchpad.energyweb.org/launchpad-by-energy-web/blockchain-infrastructure/validator-nodes/quick-start-guide).
{% endhint %}

[^1]:


---

# 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://docs.energyweb.org/ewc-validator-documentation/start-here/ewc-validator-documentation-overview.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.