> For the complete documentation index, see [llms.txt](https://docs.seda.xyz/home/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.seda.xyz/home/for-chain-operators.md).

# For Chain Operators

- [SEDA Chain Guide and Requirements](https://docs.seda.xyz/home/for-chain-operators/seda-chain-guide-and-requirements.md)
- [Installation and System Requirements](https://docs.seda.xyz/home/for-chain-operators/seda-chain-guide-and-requirements/installation-and-system-requirements.md)
- [Operating and Running a Node](https://docs.seda.xyz/home/for-chain-operators/seda-chain-guide-and-requirements/operating-and-running-a-node.md): Basic guide for operating and running the node.
- [Linking to an External Node](https://docs.seda.xyz/home/for-chain-operators/seda-chain-guide-and-requirements/linking-to-an-external-node.md)
- [Validator Onboarding](https://docs.seda.xyz/home/for-chain-operators/seda-chain-guide-and-requirements/validator-onboarding.md): SEDA Chain validators perform various signing duties for the SEDA Protocol.
- [SEDA Keys](https://docs.seda.xyz/home/for-chain-operators/seda-chain-guide-and-requirements/seda-keys.md): SEDA Chain validators may be asked to generate SEDA Keys and register their public keys to perform various signing duties in the SEDA Protocol.
- [Joining Network Using State Sync](https://docs.seda.xyz/home/for-chain-operators/seda-chain-guide-and-requirements/joining-network-using-state-sync.md): State sync offers the quickest way to join SEDA network.
- [Joining Network Using Snapshot](https://docs.seda.xyz/home/for-chain-operators/seda-chain-guide-and-requirements/joining-network-using-snapshot.md)
- [Version History](https://docs.seda.xyz/home/for-chain-operators/seda-chain-guide-and-requirements/version-history.md): History of chain versions and corresponding upgrade heights


---

# 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.seda.xyz/home/for-chain-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 `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.