Nodexo

sn106Inference & ComputeClean4Strong entry96

Miner, validator, CLI, and operator setup for Nodexo, a verified decentralized compute subnet on Bittensor

nodexo-ai/nodexo· pushed 1mo ago reg. open

Emission

0.4

TAO / day · live

Alpha

0.0107

τ · mcap 25.6K

Top-slot payout

0.004

τ per winning epoch · live

Stars

live from the GitHub API

Primary language

Python

repo-reported

Last push

1mo ago

feeds the dormancy integrity signal

Topics

—

repo-declared tags

About the repo

what the project says about itself — the input for semantic labels

nodexo-ai/nodexo· pushed 1mo ago

Miner, validator, CLI, and operator setup for Nodexo, a verified decentralized compute subnet on Bittensor

Reading this tab

scope of the data

Taonets fetches the repo's public metadata (description, topics, language, stars, last push) and the head of its README. Commit-count histories, contributor lists and release notes require the GitHub commits/releases endpoints, which the worker doesn't consume yet — those panels are coming with the ingest upgrade and are not simulated in the meantime.

README head

first lines of the default branch README, unedited

# Nodexo

Verified decentralized compute on Bittensor.

This repository contains the public operator software for running Nodexo miners
and validators, plus the CLI and setup scripts used to manage them.

Start here:

- [Miner quickstart](docs/MINER_QUICKSTART.md)
- [Validator quickstart](docs/VALIDATOR_QUICKSTART.md)
- [Endpoint security](docs/ENDPOINT_SECURITY.md)
- [CLI reference](docs/CLI_REFERENCE.md)

## Install

Miner host:

```bash
curl -fsSL https://raw.githubusercontent.com/nodexo-ai/nodexo/main/install.sh | bash
```

Validator host:

```bash
curl -fsSL https://raw.githubusercontent.com/nodexo-ai/nodexo/main/install.sh | bash -s -- --validator
```

Manual install:

```bash
git clone https://github.com/nodexo-ai/nodexo.git
cd nodexo
bash scripts/setup_miner.sh      # GPU host
bash scripts/setup_validator.sh  # CPU-only validator host
```

## Minimum Host Requirements

| Role | Minimum | Recommended |
|---|---|---|
| Miner | Ubuntu/Debian GPU host, [supported NVIDIA GPU](docs/SUPPORTED_GPUS.md), working `nvidia-smi`, Docker, 4 CPU cores, 16 GB RAM, 40 GB free Docker storage | 8+ CPU cores, 32+ GB RAM, 100+ GB free Docker storage |
| Validator | Ubuntu/Debian host, 4 vCPU, 16 GB RAM, 100 GB disk, synchronized clock, Postgres, dedicated Subtensor RPC | 8+ vCPU, 32+ GB RAM, 200+ GB disk, local or private Subtensor RPC |

Both roles require a registered Bittensor hotkey for the target subnet.
Validators should not use public Subtensor RPC for production operation. Miners
also need the public API port and rental TCP port range reachable from
validators and renters.
Validators do not require third-party API keys for normal proof verification
and weight setting.

## Networks

| Network | Runtime flag | Netuid | Chain config |
|---|---|---:|---|
| Testnet | `--subtensor-network test` | `468` | `chain_config_testnet.json` |
| Mainnet | `--subtensor-network finney` | `106` | `chain_config_mainnet.json` |

The setup scripts select the matching chain config from the network flag.
Operators can override the Subtensor transport with `--subtensor-endpoint` when
using a local node or private RPC endpoint:

```bash
--subtensor-network finney --subtensor-endpoint ws://127.0.0.1:9944
```

Validators should use a dedicated Subtensor endpoint. Public `test` and
`finney` endpoints are only suitable for setup checks or short local tests.

## CLI

For local fleet status after setup:

```bash
nodexo fleet
nodexo inventory
```