> ## Documentation Index
> Fetch the complete documentation index at: https://docs.usexfg.org/llms.txt
> Use this file to discover all available pages before exploring further.

# Installation

> Get set up by downloading, building, and running Fuego Suite on your preferred platform.

Fuego is supported across a variety of platforms including Linux, macOS, Windows, Raspberry Pi, and Android (Termux). You can build Fuego from source or run a node via Docker.

## Windows

<Steps>
  <Step title="Prerequisites">
    Install [Visual Studio 2019+](https://visualstudio.microsoft.com/) with the "Desktop development with C++" workload (ensure MSVC v142 - VS 2019 C++ build tools are selected).
    Then, install [CMake](https://cmake.org/download/) and [Boost 1.73.0 (MSVC 14.2)](https://sourceforge.net/projects/boost/files/boost-binaries/1.73.0/).
  </Step>

  <Step title="Clone and Build">
    Open the "x64 Native Tools Command Prompt for VS 2019" and run:

    ```bash theme={null}
    git clone https://github.com/usexfg/fuego-suite.git
    cd fuego-suite
    mkdir build
    cd build
    cmake .. -G "Visual Studio 16 2019" -A x64 -DBOOST_LIBRARYDIR="c:\local\boost_1_73_0\lib64-msvc-14.2"
    msbuild fuegoX.sln /p:Configuration=Release /m
    ```

    The compiled binaries will be located in the `src/Release` directory.
  </Step>
</Steps>

## Linux (Ubuntu / Debian)

<Steps>
  <Step title="Prerequisites">
    ```bash theme={null}
    sudo apt-get update
    sudo apt-get install -y build-essential cmake libboost-all-dev libssl-dev libsecp256k1-dev libjsoncpp-dev git
    ```
  </Step>

  <Step title="Clone and Build">
    ```bash theme={null}
    git clone https://github.com/usexfg/fuego-suite.git
    cd fuego-suite
    make -j$(nproc)
    ```

    Binaries are placed in `build/release/src/`.
  </Step>
</Steps>

## macOS

<Steps>
  <Step title="Prerequisites">
    Install Xcode command line tools and Homebrew, then install dependencies:

    ```bash theme={null}
    xcode-select --install
    brew install cmake boost openssl@4 secp256k1 jsoncpp git
    ```
  </Step>

  <Step title="Clone and Build">
    ```bash theme={null}
    git clone https://github.com/usexfg/fuego-suite.git
    cd fuego-suite
    make -j$(sysctl -n hw.ncpu)
    ```

    Binaries are placed in `build/release/src/`.
  </Step>
</Steps>

## Raspberry Pi (ARM64)

Running Fuego on a Raspberry Pi is officially supported (Raspberry Pi 4B/4GB RAM minimum, Pi 5/8GB RAM recommended).

<Steps>
  <Step title="Prerequisites">
    Make sure you are running a 64-bit Raspberry Pi OS. Update your system and install the required build tools:

    ```bash theme={null}
    sudo apt-get update && sudo apt-get upgrade -y
    sudo apt-get install -y build-essential cmake libboost-all-dev libssl-dev libsecp256k1-dev git
    ```
  </Step>

  <Step title="Configure and Build">
    ```bash theme={null}
    git clone https://github.com/usexfg/fuego-suite.git
    cd fuego-suite
    mkdir build && cd build
    cmake -DCMAKE_TOOLCHAIN_FILE=../arm.cmake ..
    make -j4
    ```
  </Step>
</Steps>

## Termux (Android Mobile)

You can run Fuego directly on Android devices via Termux.

<Steps>
  <Step title="Prerequisites">
    Open Termux and install the required packages:

    ```bash theme={null}
    pkg update && pkg upgrade
    pkg install git cmake clang boost openssl build-essential
    ```
  </Step>

  <Step title="Clone and Build">
    ```bash theme={null}
    git clone https://github.com/usexfg/fuego-suite.git
    cd fuego-suite
    mkdir build && cd build
    cmake ..
    make -j$(nproc)
    ```
  </Step>
</Steps>

## Docker

If you prefer containerization, Fuego provides Docker configuration.

```bash theme={null}
# Run a testnet node
docker compose -f docker/docker-compose-testnet.yml up -d

# Check logs
docker compose -f docker/docker-compose-testnet.yml logs -f fuegod
```

See the `docker/` directory for full configuration options.

***

## Running the Node

Once built, you can run the node. By default, testnet synchronization is much faster.

```bash theme={null}
# Mainnet
./build/release/src/fuegod --data-dir ~/.fuego

# Testnet
./build/release/src/fuegod --testnet --data-dir ~/.fuego-testnet
```

Wait for the daemon to fully sync before relying on accurate wallet information. You can check the synchronization status from another terminal using:

```bash theme={null}
curl -s http://127.0.0.1:28080/get_info | grep synced
```

Look for `"synced": true`.