REAX.docs Mainnet started · netuid 92
MenuOverview

Developer documentation

Build on REAX

REAX is Bittensor subnet 92 (SN92), live on mainnet since 14 October 2026. Miners serve fast, calibrated, finite-answer decision models that are Jev-compatible, and validators measure whether those models are served faithfully. Registration is open, and the source is public.

Status · 21 October 2026

REAX is live on Bittensor mainnet as netuid 92 (since 14 October 2026). Registration is open; the chain sets the burn cost, so check it before you register. Registration is a burn; the cost is set by the chain, so check it on chain or on taostats before you register. There is no public REAX testnet; practise on a local chain with the miner kit. Release 1.2 has four pools: s1-fast, s1-pro, s1-lite and s1-cpu. Our validator (UID 3) runs rounds about every 2 minutes. The source is public at github.com/reaxlabs/reax-subnet, with reax-miner-kit and reax-engine. To start mining, point your coding agent at mine.decisionmodels.io or follow Mine REAX in 30 minutes.

Release 1.2: the current mechanism

The current mechanism (release 1.2) is inference mining in four pools: Inference mining, Verification & calibration, and Competition mining. The generalist and REAX Engine tracks are paused after their Friday 30 October slots; no next crowning is scheduled. See current status on the competition page. Pages written for spec revision 0.6 describe the earlier design.

What REAX does

A REAX request carries a question with a finite candidate set: yes or no, one option out of several, or a level on an ordered scale. A miner answers with a complete probability distribution over that set, signed with its serving key. The network is built for decisions that must come back quickly and with calibrated probabilities, not for free-form text generation.

Architecture

Customer requests never reach a miner directly. They enter through the Decision Models API, are authenticated and projected by the REAX gateway, and are dispatched to an eligible miner in the right tier. Validators inject their probes through the same gateway, so a probe travels the same path as any other request.

REAX architecture Decision Models sends signed requests to the REAX gateway and router, which dispatches them to GDPR-tier or permissionless miners. Validators inject probes through the gateway, receive signed dispatch records, pair results with reference outputs, and submit weights to the Bittensor chain. EXTERNAL OWNER Decision Models API Customer ingress, tenant policy, legal notices, billing REAX CORE Gateway / router Authenticate callers · enforce tier, eligibility and capacity · project the payload · measure latency · write payload-free receipts GDPR-tier miners Admitted EU operators under contract and DPA Permissionless miners Any registered hotkey that passes conformance REAX CORE Validator Private schedules · identity and labelled probes · epoch scoring DESIGNED Reference processor Computes p_ref on byte-identical payloads MAINNET · 92 Bittensor chain Registration, permits, stake-weighted consensus signedrequest dispatch probes signed dispatch records paired p_ref commit-reveal weights REAX architecture (stacked layout) EXTERNAL OWNER Decision Models API Customer ingress, policy, billing signed request REAX CORE Gateway / router Authenticate · enforce tier and capacity · project payload · measure latency · receipts GDPR-tier Admitted EU operators Permissionless Registered hotkeys probes ↑ records ↓ REAX CORE Validator Private schedules · epoch scoring p_ref weights DESIGNED Reference processor MAINNET · 92 Bittensor chain
Solid outlines: components in the public reference code. Dashed outlines: external or designed components. The local harness uses a mocked chain snapshot and a synthetic engine.

Every miner calls its own co-located inference engine. The gateway strips caller identity and replaces the request ID and nonce with fresh per-dispatch values before anything reaches a miner. See the protocol reference for the exact envelopes.

Roles

RoleResponsibilityTrust boundary
Miner (GDPR tier)Serves admitted EU requests under contract and DPASees plaintext while inferring; admitted through an off-chain process and a signed admission snapshot
Miner (permissionless)Serves validator test items and, after a passing track record, opt-in Peer-to-Peer customer requestsAssumed to be able to log, copy or retain payloads, so it never receives EU-tier requests; customers opt in knowing this
ValidatorPrivate schedules, labelled items, identity items, verification, epoch scoring, weight submissionReceives no customer content and no organic metadata; injects probes only through the gateway; must be independent of other validators
Gateway / routerAuthenticates callers; enforces tier, eligibility and capacity; projects payloads; dispatches; measures latency; records receiptsCustomer API keys and chain keys never reach miners; never reads the emission score
Reference processorComputes reference outputs p_ref on byte-identical payloadsNever stores payloads; must be admitted like a GDPR operator for any tier whose organic traffic it shadows
Decision Models (external owner)Customer ingress, tenant policy, legal notices, billingOwns the decision to send real traffic; REAX cannot override that gate
Subnet owner / trust rootChain hyperparameters, signed trust root, policy, catalog and chain profileAn offline owner key signs issuer keys

The chain provides hotkey registration, validator permits and stake-weighted consensus over weights. It does not inspect models, prove EU location, bind a company to a DPA, or judge whether answers are correct. Those are the jobs of admission, the gateway and validators.

Tiers

GDPR tierPermissionless tier
Wire valuegdpr_euglobal_permissionless
Who can serveEU-established legal operators processing data in admitted EU countriesAny chain-registered hotkey that passes conformance
How you get inOff-chain KYB, contract and DPA, then a signed admission snapshot; chain registration is necessary but never sufficientChain registration plus a signed miner record and conformance
Traffic todayNever sent to the networkValidator test decisions, and opt-in Peer-to-Peer requests from Decision Models (single-question s1-fast only)

The Peer-to-Peer tier of Decision Models is live. A customer opts an API key in; then single-question s1-fast requests may be answered by REAX miners that have a passing track record at our validator. Every network answer is checked against our own reference GPU. EU-tier requests never go to the network.

Current status

AreaStateDetail
MainnetLive · netuid 92Netuid 92, live since 14 October 2026; Registration is open; the chain sets the burn cost, so check it before you register.
ValidatorLiveOur validator is UID 3 on an RTX PRO 6000 (96 GB); rounds about every 2 minutes
Pool s1-fastRelease 1.2Plumb-4B on one NVIDIA GPU with 24 GB or more. Several nodes per person are allowed (one hotkey and UID each)
Pool s1-proRelease 1.2mammoth-1, MIT, on an NVIDIA GPU with 48 GB or more; only RTX PRO 6000 Blackwell Server Edition measured. Run the self-check on other cards.
Pools s1-lite, s1-cpuRelease 1.28-bit GGUF on llama.cpp: s1-lite on an NVIDIA GPU with 8 GB or more incl. Jetson Orin (not yet calibrated on real hardware), s1-cpu on an x86-64 AVX2 or ARMv8.2 CPU. Capacity-based scoring applies inside every pool
CompetitionsBoth tracks pausedGeneralist paused since 30 October 2026, 16:30 UTC; REAX Engine paused after its Friday slot. No next crowning scheduled. Since the first weight set at or after Monday 2 November 2026, 14:30 UTC, inference gets 30% and follows measured customer demand; it got 40% from the first weight set after the Engine slot on 30 October until then, and 50% before that. REAX Engine remains at 20% and generalist at 30%. Unpaid portions are burned. See Competition mining.
Peer-to-Peer tierLive, opt-inDecision Models customers can opt API keys in; EU-tier requests never go to the network
TestnetNoneNo REAX testnet subnet is assigned; practise on a local chain with the kit
ImagesDisabledDisabled at the network miner pending isolated decode validation
Design specificationProvisionalThe protocol, scoring and validator pages follow the earlier design, spec revision 0.6; release 1.2 is the current mechanism. Constants are provisional
Source codePublicreax-subnet, reax-miner-kit, reax-engine; images on ghcr.io/reaxlabs

Where to go next