REAX / BUILD
Run a miner
or validator.
Everything you need to join subnet 92: the setup guide, the code, and how scoring works in detail.
01 / MINERS
Run a miner.
The easiest way in is the setup guide at mine.decisionmodels.io. It is written for you and for your coding agent: point the agent at the page and it walks you through the hardware check, renting a GPU if you need one, the wallet, registration and keeping the node running. Your coldkey and recovery phrase stay with you; the agent never needs them.
What you need
- A machine for one of four pools: an NVIDIA GPU with 24 GB or more (s1-fast, Plumb-4B), an NVIDIA GPU with 48 GB or more (s1-pro, mammoth-1), an NVIDIA GPU with 8 GB or more incl. Jetson Orin (s1-lite), or an x86-64 CPU with AVX2 / ARMv8.2 (s1-cpu). Linux, Docker and a public TCP port.
- A Bittensor wallet with enough TAO for the registration burn. The chain sets the cost; check it before you register.
- One hotkey (and UID) per node. You can run several nodes.
Release 1.2 has four pools: s1-fast, s1-pro, s1-lite and s1-cpu. Each model serves one pool; since block 9331987 (21 October 2026) one hotkey can carry 2 to 4 models and also one competition entry. s1-lite is not yet calibrated on real hardware (Jetson included). How mining works lists the pools, tier shares and hardware.
Practice first
There is no public REAX testnet. To practise, run the kit against a local chain on your own machine: reaxctl plan --mode localnet in the miner kit.
Rewards are variable and can be zero. Hardware, power and registration are your costs. Do not buy hardware expecting income.
02 / VALIDATORS
Run a validator.
A validator sends miners fresh decision items, recomputes the answers on its own reference runtime of the same pinned model, times every response on its own clock and sets weights on chain. Our validator is UID 3 on an RTX PRO 6000 (96 GB).
The validator guide on reax.dev has the setup, hardware and configuration. Customer content never reaches validators: their test items are generated fresh for every round.
03 / IN DETAIL
How scoring works.
A round
- About every 2 minutes the validator sends each miner fresh decision items (8 per round, 4 for s1-lite and s1-cpu) in one signed request. A probe looks exactly like any other request.
- The miner runs the pinned model and returns a full probability distribution over the answer options, signed with its serving key.
- The validator recomputes the answers on its own copy of the model and compares them in logit space. For s1-fast it checks all 8 items; for s1-pro a secret 3 of 8; s1-lite and s1-cpu get 4 items per round, all checked.
- Rounds feed a moving average; the moving average becomes on-chain weight.
The formula
round = (verified and D ≤ 0.20) → 0.8 + 0.2 · speed, and, inside a pool, weight = moving average × verified capacity (capped at the pool's target) within the pool's tier share.
- Correct first. An answer that drifts beyond the calibrated tolerance, a malformed, late or unsigned response, a different model or a build other than the pinned one (FP8, INT4, a different GGUF) scores zero for the round. Repeated drift resets the moving average to zero.
- Speed second. Speed adds at most 20 % of a passing round, measured on the validator's clock.
- Build-up. A new miner starts at zero and builds up over about an hour of good rounds.
- Pools. Each pool (one model on one kind of hardware) is scored on its own and has its own share.
Capacity-based scoring is live (release 1.2): inside a pool, weight is score times verified capacity, capped at the pool's target, so a hotkey with more GPUs behind it counts more (up to the cap) while many hotkeys on one machine add nothing. Live scores are on the miner leaderboard; the full protocol is on reax.dev.
Customer traffic
Decision Models customers can opt their Peer-to-Peer API keys in to network processing. Single-question s1-fast requests from those keys may then go to miners that have a passing track record at our validator (about a day of passing rounds). Our own GPU checks every network answer before it is returned. EU-tier requests never go to the network.
04 / EU OPERATORS
EU tier.
The EU tier is for contracted, EU-established companies that process data in the EU. Registration on chain is not enough. Admission needs:
- A verified legal entity that controls the serving hardware.
- A verified EU processing location and a signed data-processing agreement.
- Declared subprocessors, access controls and a security incident contact.
- The approved model revision, a bound serving key and health checks.
- A current signed admission record.
The requirements are written; admission is not open yet. An inquiry starts a conversation, not an approval. Send an operator inquiry.
05 / CODE
Code and docs.
All code is public under github.com/reaxlabs:
- reax-subnet: subnet, miner and validator.
- reax-miner-kit: the miner install kit (
reaxctl). - reax-engine: the REAX Engine. MIT License: the code is public and free for anyone to use, including companies. Mining and validating on subnet 92 are always free.
Container images are on ghcr.io/reaxlabs. Developer docs: reax.dev. To use the decision models in your own product, use the API on decisionmodels.io.