> For the complete documentation index, see [llms.txt](https://docs.nomic.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nomic.io/network/running-a-node/setup.md).

# Setup

These instructions will help you set up a new Nomic Stakenet node from scratch. If you are already running an older Nomic node, follow the [upgrade instructions](/network/running-a-node/upgrading.md) instead.

### Requirements

* \>= 4GB RAM
* \>= 100GB of storage
* Linux or macOS

### 1. Build Nomic

Start by building Nomic.

1. Install rustup if you haven't already:

```bash
curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh
```

2. Install required dependencies:

**Ubuntu/Debian:**

```bash
sudo apt install build-essential libssl-dev pkg-config clang
```

**Fedora:**

```bash
sudo dnf install clang openssl-devel && sudo dnf group install "C Development Tools and Libraries"
```

3. Clone the repo and switch to the correct directory and branch:

```bash
git clone https://github.com/nomic-io/nomic.git
cd nomic
git checkout v9.0.0
```

4. Build and install. This adds a `nomic` command to your PATH:

```bash
cargo install --locked --path .
nomic --version
```

### 2. Run your node

Start your Nomic node:

```bash
nomic start
```

This will run the Nomic state machine and a CometBFT process. For new nodes, the state-sync process will run automatically to get the node up to speed with the current chain.


---

# 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.nomic.io/network/running-a-node/setup.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.