> For the complete documentation index, see [llms.txt](https://taraxa.gitbook.io/taraxa-network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://taraxa.gitbook.io/taraxa-network/become-a-validator/consensus-node-hardware-requirements.md). # Consensus node hardware requirements ## Lite Consensus Node Minimum system requirements for the Lite Consensus Node are, * 4 CPU * 8GB Memory * 100GB SSD Most consensus nodes on the network are lite consensus nodes. The only difference between a lite node and a full node is that the lite node prunes historical state upon node restart (many community nodes periodically restar their lite nodes), while the full nodes keep everything. Beyond the state pruning, there is otherwise no difference between the full consensus node and the lite consensus node. ## Full Consensus Node Minimum system requirements for the Full Consensus Node are, * 4 CPU * 8GB Memory * 1.5TB SSD The full node's state db grows very quickly, especially when transaction load is high. Over time the storage requirements will keep growing. We of course encourage you to run a full node if storage is not too big of a concern for you, just be aware that the disk requirement will keep growing. --- # 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://taraxa.gitbook.io/taraxa-network/become-a-validator/consensus-node-hardware-requirements.md?ask=&goal= ``` `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.