> For the complete documentation index, see [llms.txt](https://stader.gitbook.io/stader/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://stader.gitbook.io/stader/ethereum/node-operator/permissioned-node-operator/pre-requisite-for-permissioned-node-operators.md).

# Pre-requisite for permissioned node operators

### The following prerequisites are required from Stader-ETHx permissioned node operators:

* Node operators are expected to generate their own validator keys for registration with Stader.
* Node operators should have Web3signer loaded with the validator keys which they wish to register with Stader. Node operators can refer the next section for Web3signer setup.
* Node operators need to create a separate validator client for Stader and set the fee recipient of the client to Stader's Socializing pool.
* Node operators must have their own staking rig, hardware solution, or cloud service to run the node/validators on the Stader Network.

{% hint style="success" %}

### **Important Note**

**Stader will generate the withdraw vault for the validators. There is no requirement for the Node Operators to create one.**
{% 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://stader.gitbook.io/stader/ethereum/node-operator/permissioned-node-operator/pre-requisite-for-permissioned-node-operators.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.