> For the complete documentation index, see [llms.txt](https://guide.dem.exchange/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.dem.exchange/technical/running-a-node/mainnet.md). # Mainnet ## Installation You can find pre-compiled node binaries [here](https://github.com/Switcheo/carbon-bootstrap/releases). The following GitHub repository provides a detailed explanation on how to install the node: {% embed url="" %} ## Node Requirements Your node requirements vary depending on whether the node is running a locally hosted Postgres instance (offchain indexer node) and if it is publicly accessible (public API/RPC node). Validator nodes (that are operated safely) are usually private, state-only nodes. Seed and sentry nodes are also typically private and state-only. On the other hand, archival and API nodes are typically public, off-chain data nodes. For nodes that require off-chain data, it is recommended to connect to a remote Postgres instance. By doing so, the RAM and disk storage requirements can be reduced to match those of state-only nodes. ## Operating System While it is theoretically possible to use any Linux distribution, only **Ubuntu 18.04 / 20.04** is officially supported. This is because the provided scripts and instructions are specifically designed for Ubuntu distributions. If you decide to use a non-Ubuntu distribution, you will need to make the necessary modifications to the setup instructions on your own. #### CPU Both **AMD-64** or **ARM-64** architectures are supported. * Private Node: **4-core vCPU** and above (e.g. AWS m6d.xlarge) * Public API/RPC Node: **8-core vCPU** and above (e.g. AWS m6d.x2large) #### RAM * State-only Node: **16GB** * Off-chain Data Node (running local Postgres server): **32GB** #### SSD * State-only Node: **1TB** * Off-chain Data Node (running local Postgres server): **2TB** --- # 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://guide.dem.exchange/technical/running-a-node/mainnet.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.