> 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/launchpad/blockchain-infrastructure/collator-nodes/collator-node-detailed-description.md). # Collator Node - Detailed Description Page describes what is a EWX Collator Node A **Collator node** is a Polkadot Substrate–based node on **Energy Web X** responsible for block production and participation in consensus. Collators author blocks, validate state transitions, and finalize on-chain activity, including workloads and economic settlement related to the Verified Compute Cloud. Collators secure the network through a combination of **self-stake and delegated stake**, aligning economic incentives with correct operation and high availability. Rewards and penalties are determined by relative stake and block-authoring performance. The **Collator Node offering in Launchpad** provides a **Collator-as-a-Service (CaaS)** experience, allowing operators to deploy and manage a production-grade collator without deep infrastructure or protocol expertise. Launchpad abstracts node provisioning, configuration, and upgrades, while enforcing secure defaults and best-practice operational parameters. This enables operators to focus on staking, monitoring, and participation in the network, rather than low-level node maintenance. --- # 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/launchpad/blockchain-infrastructure/collator-nodes/collator-node-detailed-description.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.