> For the complete documentation index, see [llms.txt](https://docs.constellationnetwork.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.constellationnetwork.io/run-a-node/validator-node-guides/delegated-staking/for-node-operators.md).
# For Node Operators
As a Node Operator, you can offer your node for delegation by following these steps:
* [ ] Configure delegated staking on your node.
* [ ] Create a delegation request to enable your node for delegation.
* [ ] Sign the delegation request using your p12 keystore private key.
* [ ] Submit the signed request to the metagraph and verify that it has been accepted.
**The nodectl utility automates these steps for you. Follow this guide to complete the setup.**
{% hint style="warning" %}
**P12 Keystore**
Delegated staking is tied to your node’s wallet public key (node ID).
If you rebuild or create a new node, your delegated staking status will remain unaffected as long as you retain your current **p12 keystore**, which holds the private and public keys designated for the Constellation Network Hypergraph or metagraph.
{% endhint %}
## [](http://localhost:3000/validate/quick-start/delegated-staking#-node-operators)
---
# 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.constellationnetwork.io/run-a-node/validator-node-guides/delegated-staking/for-node-operators.md?ask=&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.