
Overview
Registration Activity
Neuron registration trends

Neuron registration trends
The alpha price in τ, day by day, and what moved it each way.
Log change over the last 24 days +162.91%: protocol buys +0.12%, root sells −28.12%, users net +23.61%, cross-subnet +167.30%, unattributed +0.0003%. 5 days still in progress are counted as far as known.
The chart follows the alpha price in τ. Each period starts at its opening price and steps through the mechanisms below, in a fixed order, to its closing price: a step that rises pushed the price up, one that falls pushed it down, and its height is how far it moved the price. A thin line carries each close into the next period’s open; it is dashed where the two differ. The faint candle behind each period is the market’s own open, high, low and close, for context.
With many periods on screen (90 days, or hours), the steps would be too thin to read, so the chart draws the price as a line instead and colours each period by the mechanism that moved it most. Hover a period for the full step-by-step breakdown.
Not here, because they do not move the spot price: the per-block TAO injection into the pool, and burns.
All figures are log changes, not simple percentage changes, so the parts add up exactly to the total; on big moves the two differ (a 10% log fall is a 9.5% price fall).
2026-11-03 UTC, as of ≈22:39 UTC (block 9,428,489)
The day isn’t over yet, so these figures keep changing. They are in no daily total, average or rank.
Emission history is being recalculated from on-chain allocation.
Organizations running inference at scale face two challenges: ensuring model outputs remain faithful to the exact pinned weights and prompt, and distributing inference work efficiently across hardware without trust overhead. Verification through re-computation is expensive; trusting a single provider creates a single point of failure. A decentralized network of miners—each running a pinned reference model in an isolated sidecar—can serve decisions while validators verify answers by independently recomputing them in logit space. Mismatches are caught immediately and penalized, making corruption economically irrational.
REAX implements this by requiring miners to serve one of two pinned models (Plumb-4B or Surogate Rune 26B) in a containerized sidecar on loopback, with the miner process itself holding the cryptographic key and signing all responses. Validators run their own reference sidecars and recompute a secret random subset of each round's decisions, comparing logit-space distance against calibrated tolerances.
A miner whose answers drift beyond the tolerance is struck and its moving average resets; this design ensures miners cannot profitably run cheaper quantizations, cached answers, or different models without detection.
Auto-generated from the GitHub repository and may not reflect the latest changes.
REAX is a Bittensor subnet (netuid 92) where miners serve pinned reference models (Plumb-4B for s1-fast, Surogate Rune 26B-A4B v3 for s1-pro) in a runtime sidecar, and validators verify answers by recomputing them on their own reference runtime, comparing results in logit space to ensure fidelity to the exact model behavior.
REAX runs two processes per miner on one machine: (1) pinned reference runtime sidecar on loopback (port 8101 s1-fast, 8102 s1-pro), serving fresh decisions with internal HMAC authentication, and (2) reax-miner on public port, holding the hotkey, signing validator requests, forwarding to sidecar, and publishing axon/commitment on chain. Validators run their own reference sidecars (one per pool) on loopback and recompute each round's decisions to verify miner answers. Multinode mode (optional) replaces loopback with remote workers via reax-runtime-relay: gateway (miner, CPU-only, holds hotkey) signs requests and distributes to workers (each with relay + pinned sidecar on loopback) over TLS/VPN with per-request HMAC.
Competition worker (optional, separate process) measures engine images and specialist models on a shared GPU, writing results to files the validator reads in remote mode, keeping the hotkey process separate from docker socket.
The s1 mechanism ensures miners run the exact reference model by having validators recompute answers on identical weights and comparing in logit space. Fresh items per miner/round prevent copying. Spot-check verification (s1-pro) makes partial cheating unprofitable: catching one cheated item in 8 resets the EMA, costing 22 rounds to recover.
Capacity probes run all UIDs simultaneously to neutralize sybil splits: N hotkeys on one backend measure 1/N each within the shared window. Two pools (s1-fast 35%, s1-pro 65%) split inference share; tiered pools (s1-lite 15%, s1-cpu 5%) are part of the GPU tier budget. Per-coldkey diminishing returns (70% reduction per slot after the free 2) discourage farming small pools on one coldkey.
The sections above were auto-generated from the GitHub repository and may not reflect the latest changes. View repository (github.com, opens in a new tab, external site)
Verified decision-model inference on Bittensor.
This information was auto-extracted from the GitHub repository and may be incomplete or out of date. Always refer to the subnet's GitHub repository (github.com, opens in a new tab, external site) for the latest instructions.
Not yet verified: GPU count, Storage, Notes
Not yet verified: GPU count, Storage, Network, Notes
Machine-extracted from the subnet's repository docs; may be wrong or out of date. Check the repository before buying or renting hardware. Open the repository (github.com, opens in a new tab, external site) · Extracted 2 Nov 2026
Create wallet and hotkey using bittensor-cli 9.x (in separate venv from the miner)
btcli wallet new_coldkey --wallet.name reax && btcli wallet new_hotkey --wallet.name reax --wallet.hotkey miner1
Register hotkey on subnet 92 (Finney); costs current burn TAO
btcli subnets register --netuid 92 --wallet.name reax --wallet.hotkey miner1
Create shared internal token file for sidecar and miner communication
mkdir -p deploy/secrets && openssl rand -hex 32 > deploy/secrets/runtime-token && chmod 0600 deploy/secrets/runtime-token
Log in to Hugging Face with your account (required for s1-pro weights gate)
hf auth login
Download s1-fast (Plumb-4B) weights; use exact revision and --local-dir (not HF cache path)
hf download crh225/plumb-4b --revision 55de037801a8a9b9de3db5c0e16cef86210c2186 --local-dir /srv/reax/plumb-4b
Build miner and runtime sidecar Docker images from repository root
docker build -t reax:1.2.0rc3 . && docker build -f runtimes/s1-fast/Dockerfile -t reax-s1-fast-runtime .
Copy example environment file and fill in netuid, wallet names, and public IP
cp deploy/miner-s1.env.example deploy/miner.env
Start runtime sidecar and miner using docker-compose with environment variables
REAX_UID=$(id -u) REAX_GID=$(id -g) REAX_S1_FAST_WEIGHTS=/srv/reax/plumb-4b docker compose -f deploy/docker-compose.s1.yml up -d --build
Run self-check to verify setup against 640 published reference answers before registering
docker compose -f deploy/docker-compose.s1.yml run --rm --no-deps --entrypoint reax-selfcheck miner
Register validator hotkey on subnet 92
btcli subnets register --netuid 92 --wallet.name reax --wallet.hotkey validator
Add stake to validator hotkey (at least 1000 TAO for REAX_MIN_VALIDATOR_STAKE)
btcli stake add --netuid 92 --wallet.name reax --wallet.hotkey validator --amount <TAO>
Create shared internal token file for sidecar and validator communication
mkdir -p deploy/secrets && openssl rand -hex 32 > deploy/secrets/runtime-token && chmod 0600 deploy/secrets/runtime-token
Download s1-fast (Plumb-4B) reference weights
hf download crh225/plumb-4b --revision 55de037801a8a9b9de3db5c0e16cef86210c2186 --local-dir /srv/reax/plumb-4b
Build validator and s1-fast runtime sidecar Docker images
docker build -t reax:1.2.0rc3 . && docker build -f runtimes/s1-fast/Dockerfile -t reax-s1-fast-runtime .
Start s1-fast reference runtime sidecar on loopback port 127.0.0.1:8101
docker run -d --name reax-s1-fast-ref --network host --gpus all --init --restart unless-stopped --user "$(id -u):$(id -g)" -e S1M_INTERNAL_TOKEN_FILE=/run/s1m-internal-token -v "$PWD/deploy/secrets/runtime-token:/run/s1m-internal-token:ro" -v /srv/reax/plumb-4b:/model:ro reax-s1-fast-runtime
Start validator process (opens no port, needs no GPU; uses s1-fast sidecar on loopback)
docker run -d --name reax-validator --network host --init --restart unless-stopped --user "$(id -u):$(id -g)" --no-healthcheck --env-file deploy/validator.env --entrypoint reax-validator -e REAX_MECHANISM=s1 -e REAX_MODEL=s1-fast -e REAX_S1_FAST_RUNTIME_URL=http://127.0.0.1:8101 -e REAX_RUNTIME_TOKEN_FILE=/run/reax-runtime-token -v $HOME/.bittensor/wallets:/wallets:ro -v "$PWD/deploy/secrets/runtime-token:/run/reax-runtime-token:ro" -v reax-state:/state reax:1.2.0rc3
Run self-check on validator's reference runtime before enabling weights
docker compose -f deploy/docker-compose.s1-validator.yml run --rm --no-deps --entrypoint reax-selfcheck validator
Start in shadow mode (scores but does not submit weights) for first hour while miners answer
export REAX_SET_WEIGHTS=0
After 4+ rounds with miners answering and averages above 0.3, enable weight submission
export REAX_SET_WEIGHTS=1