> For the complete documentation index, see [llms.txt](https://energy-web-foundation.gitbook.io/ewc-validator-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://energy-web-foundation.gitbook.io/ewc-validator-documentation/ewc-governance/ewc-validator-node-operational-functions.md).

# EWC Validator Node Operational Functions

EWC validator nodes can:

* Establish consensus about the state of the network by verifying the work / behavior of other validator nodes;
* Reject blocks / transactions that violate input/output protocols defined by AuRa and the EVM state transition function; 
* Implement permissioning functions as described [here](https://openethereum.github.io/Permissioning) (note: permissoining functions can only be implemented via a majority governance decision). 

EWC validator nodes CANNOT:

* Inspect or approve the contents of individual transactions;
* Unilaterally verify transactions (any given transaction is only finalized after n/2 blocks, with n=total validators);
* Associate identities with on-chain accounts;
* Unilaterally modify account permissions, network topology, or network state.


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://energy-web-foundation.gitbook.io/ewc-validator-documentation/ewc-governance/ewc-validator-node-operational-functions.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.