Build the
network.

Permissionless participation is the intended open-network path. Capable operators will serve typed decision models and answer synthetic validator probes. A permissionless miner will not receive requests from the GDPR tier.

Hardware and model requirements

• Python 3.10 or newer is required for the private reference package.
• Model support, accelerator compatibility, memory requirements and throughput targets remain under validation. No GPU purchase is recommended for REAX yet.
• The prototype adapter expects an operator-controlled s1m-engine over loopback HTTP or HTTPS. The engine is a separate component; installing the reference package does not install model weights or start inference.
• Keep service credentials in permission-restricted mounted files. Do not place them in commands, source control or logs.

Local prototype setup

There is no public miner download or live join command. If you have been granted access to the private prototype, run these commands from its checked-out repository:

python3 -m venv .venv
. .venv/bin/activate
python3 -m pip install -e '.[server]'
python3 -m unittest discover -s tests -v

This installs the reference Python package with its server extra and runs local checks. The reax.dev quickstart is the maintained version of these steps. It does not start a network miner, register a wallet, join testnet or set weights. Use synthetic inputs only. Do not connect an existing wallet or submit real TAO.

From prototype to participation

1. Check the released model licences and measured hardware requirements when available.
2. Run the reviewed miner service and synthetic compatibility checks once distributed.
3. Use the published testnet identifier and fresh test-only credentials after registration opens.
4. Review live participation rules before any later mainnet action.

Steps 1–4 are a future onboarding path. No registration instructions, public binary or mainnet activation is available yet. Email an operator inquiry if you want to help test the prototype.

Scoring and costs

In the provisional design (specification revision 0.6), faithful serving of the approved model is a hard gate, and weight follows availability, latency capped at the reference and verified capacity. How miners earn weight explains the mechanism. Final parameters are pending review. Network incentives are not a guarantee of income; operating hardware incurs costs.

Regulated traffic requires more than an EU address. The proposed GDPR admission path checks the operator, the processing location, contractual terms and the exact serving identity before routing can be enabled.

• Verified legal entity and authority to operate the capacity.
• Verified EU processing location and an approved data-processing agreement.
• Documented subprocessors, access controls and incident contact.
• Approved model revision, serving public key, health checks and location evidence.
• A current signed admission record. Evidence hashes alone do not prove that evidence is genuine or current.

These are proposed admission requirements. The admission issuer and operational review workflow are not live. An inquiry is not approval, certification or a promise of traffic.

Validators compare miner outputs with the reference model's outputs on identical synthetic items; a sealed labelled pool is used only for the quality check. Cross-model agreement is a diagnostic signal, not proof that an answer is correct. Customer payloads are designed to stay out of validation questions.

What you can prepare

1. Use an isolated environment with synthetic inputs and repeatable timing.
2. Review the task types: yes/no probability, finite-option choice and ordered score.
3. Check that responses preserve the requested labels, model revision and serving identity.
4. Wait for the reviewed probe runner, chain adapter and testnet instructions before submitting network weights.

Authorized prototype reviewers can run the same local setup and unit-test commands shown above. Those checks are not a running validator or a Bittensor network integration.

REAX is intended for typed decisions: yes/no probabilities, choices from a fixed set and ordered scores. System1 Models is the planned first product integration. REAX does not currently route its customer traffic.

The System1 Models website is available over HTTPS. Check that site's current access and service status. A working website link does not mean public signup or REAX routing is ready.

There is no public REAX inference endpoint or SDK release today. Use synthetic integration tests only until a reviewed staging route is provided.