> For the complete documentation index, see [llms.txt](https://docs.co-ophive.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.co-ophive.network/user-guide/compute-nodes/run-a-node.md).

# Quick Start

The testnet has a base currency of ETH, as well as a token called HIVE. HIVE is used for payments and collateralization.

## Prerequisites

* A private key and funds for the testnet
  * See the instructions in [Quick Start](/user-guide/clients/quick-start.md) to set up MetaMask and use the faucet to receive initial funds
* Linux (latest Ubuntu LTS recommended)
* Docker
* Nvidia GPU
* Nvidia drivers
* Nvidia docker drivers

### Install Bacalhau

```
cd /tmp
wget https://github.com/bacalhau-project/bacalhau/releases/download/v1.0.3/bacalhau_v1.0.3_linux_amd64.tar.gz
tar xfv bacalhau_v1.0.3_linux_amd64.tar.gz
sudo mv bacalhau /usr/bin/bacalhau
sudo mkdir -p /app/data/ipfs
sudo chown -R $USER /app/data
```

### Install CoopHive

```
curl -sSL -o hive https://github.com/CoopHive/hive/releases/download/v0.1.12/hive-linux-amd64
chmod +x hive
sudo mv hive /usr/bin/
```

### Write .env file

Create a .env file for your node. `/app/coophive/resource-provider-gpu.env` should contain:

```bash
WEB3_PRIVATE_KEY=<your private key>
```

Caution: do not use the same key for both client and compute node, even for testing.

### Install systemd unit for Bacalhau

Open `/etc/systemd/system/bacalhau.service` and paste the following:

```
[Unit]
Description=CoopHive v0
After=network-online.target
Wants=network-online.target systemd-networkd-wait-online.service

[Service]
Environment="LOG_TYPE=json"
Environment="LOG_LEVEL=debug"
Environment="HOME=/app/coophive"
Environment="BACALHAU_SERVE_IPFS_PATH=/app/data/ipfs"
Restart=always
RestartSec=5s
ExecStart=/usr/bin/bacalhau serve --node-type compute,requester --peer none --private-internal-ipfs=false

[Install]
WantedBy=multi-user.target
```

### Install systemd unit for GPU provider

Open `/etc/systemd/system/coophive-resource-provider.service` and paste the following:

```
[Unit]
Description=CoopHive v0 Resource Provider GPU
After=network-online.target
Wants=network-online.target systemd-networkd-wait-online.service

[Service]
Environment="LOG_TYPE=json"
Environment="LOG_LEVEL=debug"
Environment="HOME=/app/coophive"
Environment="OFFER_GPU=1"
EnvironmentFile=/app/coophive/resource-provider-gpu.env
Restart=always
RestartSec=5s
ExecStart=/usr/bin/coophive resource-provider

[Install]
WantedBy=multi-user.target
```

Reload `systemd`'s units/daemons. This needs to be repeated if the `systemd` files above are modified.

```
sudo systemctl daemon-reload
```

Start `systemd` units:

```
sudo systemctl start bacalhau
sudo systemctl start coophive-resource-provider
```

Use `systemctl` to check the status, and debug with `journalctl` if needed. For example,&#x20;

`sudo journalctl -uf coophive-resource-provider`&#x20;

will stream the output from your CoopHive node. Records of the resource provider accepting jobs can be found in the logs.

## Security

### Allowlisting Modules

Set the environment variable `OFFER_MODULES` in the GPU provider to a comma separated list of module names of allowed modules.


---

# 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://docs.co-ophive.network/user-guide/compute-nodes/run-a-node.md?ask=<question>&goal=<endgoal>
```

`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.