THE REAX NETWORK IN DEVELOPMENT

Decisions at
reflex speed.

A Bittensor subnet for fast, calibrated decision models, in development.

01 / THE OPPORTUNITY

Millions of small decisions.
Most don't need a giant model.

AI agents route requests, choose next actions, and decide when to escalate. They need a fast, calibrated answer to a specific question.

Route this request?Escalate this case?Choose the next action?

02 / THE NETWORK

Intelligence
that reacts.

REAX is being built to serve approved open decision models across a peer-to-peer network of independent operators.

Data-centre miners
Home GPUs
Contracted EU operators for regulated traffic

The subnet is in development and not yet registered on any Bittensor network. The EU tier is intended for contracted operators once data-processing terms and admission are in place.

03 / HOW IT WORKS

A reflex, in four moves.

01

A request asks

A Jev-compatible question with a finite candidate set: yes or no, one option from a fixed list, or an ordered score.

02

The gateway routes

It authenticates the caller, strips everything a miner does not need, and picks an eligible miner in the right tier.

03

A miner answers

It runs the approved model and returns a full probability distribution over every candidate, in an envelope signed with its serving key.

04

Validators measure

They check faithful serving, availability, latency and capacity, and turn the ledger into on-chain weights. Customer content never reaches them.

This is the design in specification revision 0.6, which is provisional and still changing. Today it runs only as a private local rehearsal with simulated miners and no chain. Check the current status.

04 / INCENTIVES

How miners
earn weight.

Validators do not reward claims. They measure how faithfully, reliably and quickly a miner serves the approved model, and the chain turns those measurements into weights.

A

Every request could be a test.

Probes and real requests share one path Real requests and validator probes both enter through the gateway, which sends the miner one identical envelope with no probe marker. A dashed branch shows sampled re-execution on a reference processor, which is designed but switched off. REAL REQUESTS customer ingress VALIDATOR PROBES scored test items GATEWAY one ingress · TLS · egress · pool NO PROBE MARKER IDENTICAL ENVELOPE MINER full distribution, signed REFERENCE PROCESSOR 2% re-run · switched off Probes and real requests share one path Real requests and validator probes both enter through the gateway, which sends the miner one identical envelope with no probe marker. A dashed branch shows sampled re-execution on a reference processor, which is designed but switched off. REAL REQUESTS customer ingress VALIDATOR PROBES scored test items GATEWAY one ingress · TLS · egress · pool NO PROBE MARKER MINER full distribution, signed REFERENCE PROCESSOR 2% re-run · switched off

DESIGNED

Hidden probes

Validators inject scored test items through the gateway on the same path as real traffic: the same ingress identity, TLS configuration, egress addresses and connection pooling. The envelope a miner receives carries no probe or organic marker, so a miner cannot tell a probe from a real request by how it arrives. Today the open tier carries synthetic traffic only, so every request there is validator-generated and checked.

DESIGNED · SWITCHED OFF

Sampled re-execution

For a small, seed-selected fraction of real requests (provisionally 2%), the gateway sends the same bytes synchronously to a reference processor and compares the two answers in memory. Validators receive only an aggregate verdict per miner; payloads and answers are not stored. It stays off until the reference processor is admitted for the tier and listed as a DPA subprocessor, System1 acceptance covers it and a privacy review approves the aggregate outputs. It is mandatory before any real traffic.

B

Gain is multiplied, not averaged.

gain = gates × availability × (0.8 + 0.2·L) × verified capacity

  1. Gatespass / fail

    Right tier, valid signatures, and the approved model served faithfully, compared against a reference. A substitute that drifts beyond tolerance (placeholder values today) is frozen, then zeroed after a second failing window.

  2. AvailabilityA ≥ 50%

    The share of scheduled requests answered validly and on time. Below 50% (provisional) a miner is not eligible; above it, availability scales gain directly.

  3. Latency0.8 + 0.2·L

    Full credit at reference speed, within a 10% tolerance (provisional). A faster substitute gains nothing on latency (spec target; the current code does not yet cap at the reference).

  4. Verified capacityburst-audited

    Throughput (κ) measured in synchronized, audited bursts of fresh items, in reference units. Until its adversarial simulations pass, capacity counts as 1 for everyone, and no external miner receives weight on a public network until capacity measurement is live.

C

From gain to weight.

Ramp-up

New or improving miners phase in over two epochs. Decreases apply at once.

Operator-group cap

Miners are grouped by coldkey, or by contracted operator. One group holds at most 40% of weight (provisional).

Abstain, don't guess

If fewer than three groups qualify, validators set no weights rather than concentrate them.

All figures are provisional parameters of design specification revision 0.6. They live in signed policy and may change before the design is frozen. No miner outside the local rehearsal is scored today.

05 / TWO TIERS

Two tiers.
One standard of serving.

GDPR TIER

Contracted EU operators.

Who
EU-established legal entities that process data in the EU.
Admission
Off-chain business verification, operator contract and data-processing agreement, then a signed admission record. Chain registration alone is never enough.
Traffic
Intended for regulated requests once admission, legal review and System1 acceptance are in place.
Status
Requirements drafted. Admission is not live.
Send an operator inquiry

OPEN TIER

Permissionless miners.

Who
Anyone with a registered hotkey who passes conformance checks.
Admission
Conformance, then a first complete fidelity window. Registration proves neither location nor legal identity.
Traffic
Synthetic traffic only for now. Never personal or GDPR-tier data.
Status
Pre-release documentation. No subnet is registered yet.
Read the pre-release quickstart

EMISSIONS ARE NOT BILLING

Bittensor emissions are the network's incentive mechanism. They are kept separate from customer billing, which is in fiat and never reads weights. REAX makes no promises about rewards, their amount or their value, and nothing on this site is investment advice. Whether contracted GDPR-tier operators also receive emissions is an open legal question.

06 / ROADMAP

Gates,
not dates.

Each stage opens only when the stage before it has passed its gates. Every rollout gate is closed today, and we publish no dates.

  1. 01

    NOW · IN PROGRESS

    Design and local harness

    Design specification revision 0.6, provisional and not frozen. A private rehearsal runs three simulated miners and one validator on synthetic traffic, with no chain.

  2. 02

    NEXT · NOT REGISTERED

    Testnet

    The official Bittensor testnet, with test TAO and throwaway keys only. Follows a frozen design, a full local harness and adversarial simulation.

  3. 03

    PLANNED

    System1 staging

    Synthetic staging traffic through System1's staging integration, with the System1 owner's consent. No customer data.

  4. 04

    NOT LAUNCHED · NEEDS APPROVAL

    Mainnet

    Registration needs explicit approval of cost and owner key, plus capacity measurement that has passed simulation. Not launched.

  5. 05

    INTENDED · G5 GATES

    Decentralized global tier

    Intended: the open network serving real System1 global-tier traffic, only once the G5 acceptance gates pass: signed System1 acceptance, legal review, sampled re-execution on and capacity measurement live.

  6. 06

    PLANNED · NEW SPEC VERSION

    Finetuning service & miner competition

    Planned: a finetuning service that produces custom fine-tuned decision models, with miners competing to produce better fine-tuned models. Not yet specified; it needs a new major version of the specification (the v1 catalog is closed).

08 / TAKE PART

Build the reflex.

EU operators can start a conversation about the GDPR tier today. Open-tier miners and validators can follow the pre-release developer docs ahead of testnet.

The docs describe the pre-release path; source code is private and no REAX subnet is registered yet. Questions first? Read the FAQ.

09 / WHO WE ARE

Designed for an open network.

REAX is being built as a Bittensor subnet. The REAX website and development work are operated by productivity-boost.com in Germany. Subnet ownership and mainnet operating arrangements are not announced.