COMPUTE FOR REAX · POWERED BY YOUR GPU

Point your agent here. Mine with your own GPU.

Give your coding agent one link. It checks your machine and sets up a miner for REAX, a peer-to-peer inference network on Bittensor. You keep your keys and approve every payment.

Check whether this computer can mine REAX (Decision Models) and prepare a setup plan: https://mine.decisionmodels.io

NVIDIA GPU · 24 GB+Linux (Windows via WSL2)Not live yet — launching soon

A coding agent is an AI tool that can run commands on the computer you authorize. Works with Claude Code, Codex CLI, Cursor and Gemini CLI. New to coding agents? Start here.

Prefer to do it yourself? Read the playbook →

Illustrative agent session: > Check this computer for REAX mining: mine.decisionmodels.io ✓ Read the playbook (agent.md) ✓ Checked hardware: Linux, NVIDIA RTX 4090 · 24 GB ✓ Reviewed hardware, wallet and ports plan → Setup and the free practice run open at launch I stop here until the source is public. Your keys stay with you.

Illustration of a typical session. Today: checks and a plan; setup opens at launch.

HONEST STATUS

Launching soon.

The REAX subnet (a network within Bittensor) is not live on the main network yet, and the miner code and images are published at launch. Today your agent can check your machine and tell you exactly what you need — hardware, wallet, ports — so you are ready on day one. Setup, a free practice run on a local chain, and the real network all open at launch; this page then switches over.

01 / THE SETUP

What happens

  1. 01
    AGENT

    Check hardware

    Checks your GPU, driver and the requirements.

  2. 02
    AGENT

    Install the kit

    At launch: Installs the pinned miner kit and verifies its checksum.

  3. 03
    YOU

    Create your wallet

    You create your wallet on a separate trusted device.

  4. 04
    YOU

    Approve registration

    At launch, you review the fee and sign in your wallet.

  5. 05
    AGENT

    Start and verify

    At launch: Starts the miner, checks its answers and keeps it updated.

Your agent can check this machine today. Setup opens at launch.

Real output of reaxctl doctor on recorded pre-launch sample machines — not a live miner.

24 GB NVIDIA GPU

$ ./reaxctl doctor
Verdict
  [ok] Host checked. The free rehearsal needs the REAX source, which is private until launch.
What works today (rehearsal)
  Localnet rehearsal is possible with the pinned source and tools.
What is needed for real mining
  Check the release descriptor: the network must be live, with a netuid and public images.
Next
  reaxctl plan  # Review what you can prepare today.

No GPU (hardware check)

$ ./reaxctl doctor
Verdict
  [ok] Host checked. The free rehearsal needs the REAX source, which is private until launch.
What works today (rehearsal)
  Localnet rehearsal is possible with the pinned source and tools.
What is needed for real mining
  No usable NVIDIA GPU detected; AMD and Apple GPUs are unsupported for mining.
    Fix: Use a Linux machine with an NVIDIA GPU and driver R580+ (a Mac or AMD machine can only act as a controller): https://www.nvidia.com/en-us/drivers/
  Requires 1 NVIDIA GPU(s) with 24 GB VRAM and R580+ driver.
    Fix: Select a pool matching your GPU capacity; supported hardware is listed in the release descriptor.
  Check the release descriptor: the network must be live, with a netuid and public images.
Next
  reaxctl plan  # Review what you can prepare today.

The 24 GB card qualifies for s1-fast hardware; launch and runtime checks still apply. No-GPU sample shows the source availability note and hardware blockers.

02 / YOUR MACHINE

Will my computer work?

These are the bundled release's requirements for s1-fast. Availability follows the release descriptor. Your agent still checks the exact GPU, driver, container, model and network.

Component Requirement
GPU One compatible NVIDIA GPU, ≥24 GB VRAM (GPU memory)
Driver R580+ for CUDA 13
Host 4 CPU cores · 32 GB RAM · 20 GB free disk
Network Public IP · inbound TCP 8091 · synchronized clock
OS Linux x86_64; Windows via Windows Subsystem for Linux 2 (WSL2) is conditional and not yet tested by us end to end

A free local-chain practice run opens when the source is published at launch. A Mac can control an authorized remote NVIDIA Linux host.

03 / YOUR KEYS

You keep the keys

  • Your coldkey (the key controlling your funds) stays on a separate trusted device.
  • The agent never sees your recovery phrase or coldkey private file.
  • A human approves every payment.

New to mining? Read the glossary →

Choose a wallet and understand the signing boundary →

Your coldkey stays home; the hotkey signs on the miner A wallet on your trusted device holds the coldkey, controls funds and approves payments. A separate mining machine holds only the hotkey and signs answers. The coldkey never crosses the dashed boundary. YOUR TRUSTED DEVICE Coldkey Funds, approves payments STAYS HOME MINING MACHINE Hotkey Signs answers OPERATIONAL KEY ONLY COLDKEY NEVER CROSSES Separate devices, separate keysYour trusted device holds the coldkey for funds and payment approval. It stays home and never crosses to the mining machine. The miner holds only the hotkey to sign answers. YOUR TRUSTED DEVICEColdkeyFunds, approves paymentsSTAYS HOME COLDKEY NEVER CROSSES MINING MACHINEHotkeySigns answersOPERATIONAL KEY ONLY

04 / A CLEAR VIEW

Rewards and risks

Mining receives variable rewards from the REAX subnet (a network within Bittensor), with risks. Emissions depend on competition and can be zero. Hardware, electricity, connection costs and a non-refundable registration burn are yours to weigh.

Read the risks before paying →

05 / MACHINE ENTRY POINTS

For agents

Entry point What it gives you
agent.md Canonical playbook, approvals and pinned commands
llms.txt A short map of the docs
mine.json Status, steps, requirements and rules
releases/current.json The kit's bundled release descriptor
install.sh Readable pinned-archive download; read before running
Kit source Review the Python commands
WebMCP tools Optional read-only tools; browser support varies

Local agents can act on the selected machine. Cloud/browser agents can prepare a plan; chat-only agents can explain steps. The agent must say where its commands run. WebMCP does not grant a local shell or permission to spend.

Kit 0.1.1 · subnet release 1.1.0rc2
commit 1ea378f0fcaa3f84d9482091285fbd5a7bc6f79b
SHA-256 bfed4c8c7e5efb42386af439e8f713e309a8416755597a6fd1ef627f13c280d7