SUBNET TRACKER · All subnets
SN92 · REAX
Every Bittensor Daily mention of SN92 REAX, newest first. Price changes are snapshots from each edition.
24h change +9.91%
- What happened
- SN92 (REAX) closed out its last competition round before pausing both tracks: Engine v2 crowned uid 240 as champion with a 2.08x average speed-up over the reference engine, confirmed in a second measurement, while the Thursday generalist slot ended in a tie between uid 83 and uid 114 after two other entries were removed for missing the required copy-rule margin. During the same period, a validator bug tied to the switch of inference model s1-pro from Rune to mammoth-1 cut weights for 57 s1-pro miners for about 2.5 hours; the team paid a one-off make-good of 41.8 alpha to the affected miners. Separately, the subnet owner put in place a 'lock instead of burn' emission change, raising the owner share to 26% and the miner share to 33%, with the validator share unchanged at 41%, locking surplus owner emission on-chain rather than burning it. Over 9 days, 158 models from 85 miners were submitted, with the median entry beating base model mammoth-1 by +7.2 points.
- Community
- Community members pressed the team on repeated delays to the Engine v2 crowning, which pushed the measurement and results timeline back several hours and required extra GPU boxes. A community member also flagged an edge case in the generalist 'seated champion plus margin' rule when scores cluster near a ceiling, and another questioned on-chain transactions later identified as the make-good payment.
- Official
- The team confirmed the validator bug behind the s1-pro weight cut, described it as their fault, and detailed the make-good payment of 41.8 alpha. It also acknowledged the generalist tie-break rule issue as a fair point for future rounds and announced the owner-share emission change as agreed and live on chain.
24h change +17.61%
- What happened
- SN92 (REAX) announced a shift away from its engine and generalist competitions toward revenue-generating inference and business development, with both competitions set to pause after Friday's crowning. The team also clarified reward decay rules for new champions (full share for 3 days, linear decay to zero over the following 4 days) and confirmed mammoth-1 hardware requirements, allowing 48GB-class cards such as L40S, RTX 6000 Ada, and A6000. Infrastructure issues, including container timeouts and a disk problem, delayed measurement of submitted entries ahead of the crowning, prompting the team to add extra measurement machines.
- Community
- Community members asked for details on the evaluation schedule, payout rules, and whether both competition tracks would end, and one miner suggested the pivot should not come at the expense of research. Another miner raised the subnet's current token economics, while others pressed for clarification on specific delayed entries during the measurement backlog.
- Official
- The team said the pause is not a final end to competitions but a shift to focus spending on inference, marketing, sales, and customer acquisition, with competition insights to be applied later. It confirmed that during the pause, the share previously allocated to competitions is burned, and that infrastructure issues causing measurement delays were on its side, with extra machines added to clear the backlog before the crowning.
24h change −13.73%
- What happened
- SN92 (REAX) rolled out Engine rules v2.0, expanding the Engine track to score five models with a weighted geometric mean, effective after the Oct 27 crowning. The subnet also doubled GPU speed caps for its s1-pro and s1-fast pools, deploying the change early via validator release 1.2.0rc11.post7.1. Multiple new Engine champions were crowned (uid 221, uid 164, uid 62), and the team shipped a hotfix after a keep-alive bug caused a former champion to be deregistered shortly after committing a new entry. SN92 also announced that the inference share of miner emissions will drop from 50% to 40% starting Oct 30, with the freed emissions burned.
- Community
- Community members asked whether a malfunction was behind declining emissions and questioned who was selling alpha, prompting a reminder from a community member that discussions framed around price or investment returns are not permitted in the channel. Miners also raised technical questions about the new Engine rules, including caching behavior for the mammoth-1 model, and about slot timing for entries with private repositories.
- Official
- The team said no malfunction occurred, that the alpha emission per block is fixed by the protocol, and that the operator share pays for running the subnet. It apologized for the keep-alive bug that caused a champion's deregistration and said the emissions-split change aims to align miner payouts with actual customer demand for inference.
24h change −3.69%
- What happened
- SN92 (REAX) saw two new REAX Engine champions crowned on the Generalist track: uid 57 at 12:42 UTC and uid 223 at 16:41 UTC. A separate submission (uid 196) was denied an award after the team found that undoing a per-channel rescaling of its MLP weights made it mathematically identical to an earlier submission. Separately, REAX released REAX 1.2, an open-weights fine-tune of REAX 1 under Apache-2.0, alongside REAX 1.1.
- Community
- Miners asked about inference weighting and the status of award approvals, with one miner asking directly why uid 223's award was taking longer than uid 57's. A validator also warned the channel about fake support-ticket links circulating in replies, telling members not to follow them or share keys and seed phrases.
- Official
- The team explained that uid 57's award was approved quickly because its runtime and kernel sources were already public, while uid 223's approval was held pending publication of source for 14 new compiled kernels; the award was approved once the source check passed. The team also detailed why uid 196 was denied an award, citing an identical computation after undoing a weight rescaling.
Read the full edition: SN15 (ORO) Bans 32 Accounts After Spend-Limit Manipulation Audit →
24h change −18.29%
- What happened
- The team confirmed that eval v5 binds from Monday, Oct 26, 14:30 UTC, after a second validation check, and published the eval v5 format, a 300-item dev set and the reference scorer in the reax-subnet repository. Validator release 1.2.0rc11.post4 went live, with other validators asked to upgrade. Generalist track places 2 and 3 emissions went live for uid 160 (17%) and uid 113 (8%) after a delay, and uid 164 was crowned new REAX Engine champion at 3.43x reference engine throughput, surpassing the previous champion uid 176 (3.22x). Decision Models (SN92) went live on New York Token Exchange via TrustedRouter.
- Community
- Miners discussed that roughly 80% of miners in the inference pool are losing money, with some miners reporting continued break-even or profitable results depending on their setup and GPU costs. Some miners asked about the status of the delayed place-2 and place-3 emissions before they went live.
- Official
- The team explained the losses as part of an intended equilibrium where inefficient inference setups exit while efficient ones remain profitable, and pointed miners toward efficient engines, owned or cheap hardware, and serving multiple models. The team also confirmed the eval v5 timeline, validator release, and emission start times for the generalist track.
24h change −9.99%
- What happened
- SN92 (REAX) fixed a validator bug that had zeroed emissions for several engine-track UIDs after an outdated engine state file was read. A statistical tie among uid 250, uid 116 and uid 199 in the generalist opening playoff led the team to reverse its initial single-champion decision and name all three co-champions. On the engine track, uid 56's champion award was held because its kernel binaries lacked published source, then approved after the code was released under an MIT license; a new engine champion, uid 176, was crowned afterward. The team also announced a growing EU tier requiring miners to be EU-registered companies with EU-located GPUs, published a public miner FAQ, and set fixed biweekly crowning slots for the generalist track.
- Community
- Several miners and a validator pressed the team for the underlying numbers, arguing that uid 116's higher playoff score should have decided the generalist opening rather than commit order, while others questioned why only three entries received an extension draw when additional entries were within the same noise level. Separately, some miners reported that mining has become unprofitable across various GPU types.
- Official
- The team published the full playoff scores and standard errors, reversed the initial sole-champion call in favor of three co-champions, and later detailed the exact score margin used to define the statistical tie group.
24h change +3.81%
- What happened
- SN92 (REAX) released REAX 1, an open decision model built on Perplexity Decider v1.2, as the base model for a new generalist model training competition that opened at 13:00 UTC with 12 entries in the opening cohort. The team also restructured champion-protection rules so that champions and former champions keep a 75/17/8 reward split and are shielded from immediate deregistration. During the week the subnet also had three validator-side issues: a scoring-display bug in release rc10, a capacity-probe timing bug affecting about 50 high-UID hotkeys, and a scoring-order bug that evaluated post-opening entries before the opening cohort. The team announced a four-part rule update, later corrected to take effect Friday, October 23, 2026, 13:00 UTC.
- Community
- Miners had pressed the team for weeks over co-champions losing emissions and registration fees upon deregistration, and some asked for protection to extend beyond a single round. Community members also flagged the rc10 scoring display issue and the capacity-probe anomaly, both of which the team confirmed and fixed; a miner's suggestion to reward 2nd and 3rd place in the opening generalist playoff was adopted.
- Official
- The team rolled back the rc10 release within about an hour, confirmed no miner lost weight, and later compensated affected miners roughly 6.5 alpha from the owner's own funds; it also confirmed and fixed the scoring-order bug, giving pruned opening-cohort entries a re-entry window until 07:30 UTC on October 22.
24h change −6.13%
- What happened
- SN92 (REAX) opened a new engine-speed competition track at block 9326382 (18:00 UTC), requiring miners to build faster inference engines for s1-fast, and announced it will replace its separate use-case competition tracks with a single generalist decision-model track opening around Oct 23. The first engine evaluation batch returned inconclusive results after a firewall blocked image registries, with batch 2 proceeding once fixed. UID 198 and UID 4 were named co-champions of the first engine track round following a disputed block-hash tie-break, and the team said it would remove the hash-based lottery for future rounds. SN92 also released a feature allowing one hotkey to be served by multiple machines, aimed at easing registration pressure from miners needing separate hotkeys per GPU.
- Community
- Miners debated the chain-set registration burn fee at length, with some asking for it to be raised and others arguing it is too high and shuts out smaller participants during the engine-competition rush, including proposals for per-UID penalties or temporary caps. A separate dispute followed the engine track's tie-break decision, with some miners questioning whether the hash-based ordering was fair.
- Official
- The team defended the registration fee as a chain-determined market mechanism meant to prevent slot flooding and unfair deregistrations, confirmed the engine track opening at block 9326382, explained the hash-based tie-break that led to the co-champion decision and said the hash lottery would not be used again, and announced that SN92's decision models are now integrated with the Antseed platform, including an EU tier and an auto-router feature.
24h change −11.02%
- What happened
- SN92 (REAX) activated Eval v3 for its DF and RA specialist tracks, adding private real-data items, a generalisation penalty and a tougher crowning threshold (2.75 SE over draws). A new rule takes effect Oct 20 18:00 UTC requiring challengers close to the champion's weights to also beat it on correctness, closing a gap where a near-identical model won on calibration alone. The REAX engine track is set to open Oct 20 18:00 UTC (fallback Oct 21), with the team reporting a 6x inference speedup over the reference server baseline. UID 67 passed its confirmation draw and became the new RA champion, pending copy check and approval.
- Community
- Miners questioned the fairness of the prior DF crowning, arguing the new champion was effectively a copy of the previous one with only calibration differences. Separately, a miner noted that current RA models appear to be derivatives or transforms of two base models, raising concern about originality, though they added this may not be an issue if the models perform better.
- Official
- The team confirmed Eval v3 went live at 18:08 UTC and that the engine track opens Oct 20 18:00 UTC with a fallback to Oct 21. It also corrected an earlier post implying the engine competition had already started, clarifying that submissions only begin counting once the track opens.
24h change +3.33%
- What happened
- The team is rolling out worker changes to the champion-selection logic after a miner reported that the failure-counter reset allowed a model to dodge the 3-failure rule and keep its champion status. The planned fix will count start-up failures over a rolling window instead of resetting them, give champions an immediate retry on failure, and exclude infrastructure errors from failure counts. Release 1.2.0rc9 went live on the reference validator, doubling the per-hotkey speed cap to 1,280 decisions/s for s1-fast and 320/s for s1-pro. Separately, the team is adding private tasks to evaluation effective Oct 19 at 18:00 UTC after testing found the champion model scores 75 on regular items but only 36 on held-out private tasks, a gap of 40 points.
- Community
- A miner described the champion-selection bug in detail, citing a monitoring agent that showed the issue persisting on one UID since 07:48 UTC, and said another model had been kept out of the champion position as a result. Other community members raised questions about the emission split and the pace of speed-cap increases relative to hardware costs.
- Official
- The team confirmed the bug, outlined the planned worker-release fix, and said it would not change the inference/competition emission split or raise the speed cap further until it reviews a few days of data following the current 2x cap increase.
24h change +15.04%
- What happened
- SN92 (REAX) shipped validator update 1.2.0rc8, speeding up the competition evaluation queue and adding keep-alive protection for up to 8 waiting entries per track, and announced release 1.2.0rc9, which will double per-hotkey inference speed caps (s1-fast 640 to 1,280, s1-pro 160 to 320 decisions/s) on Oct 18, 2026. Three days after going live, the network reported 217 miner slots serving decision models and 65 independent miner wallets earning. The first model-training competitions crowned champions in demand forecasting (UID 71, score 91.1 vs a 38.2 baseline) and risk assessment (UID 251, score 64.2 vs 31.7), both approved. The team also raised the registration fee growth rate and extended the immunity period to address high daily re-registrations, and fixed a risk-assessment evaluation queue stall caused by an unreachable repository.
- Community
- Miners asked why UID 71 was named champion despite a lower raw score than some competitors, questioned why champions had not yet received rewards, and reported hotkeys being deregistered while still awaiting evaluation. Separate exchanges included accusations between miners over an alleged alt account and copied models, along with complaints about moderators being summoned unnecessarily.
- Official
- The team explained that the champion is decided by a head-to-head playoff rather than raw first-draw scores, confirmed both crowns as approved, and said it would close a gap that let entries be pruned while still waiting for their first evaluation.
24h change −3.26%
- What happened
- The team opened two SN92 (REAX) competition tracks, demand forecasting and risk assessment, at 12:00 UTC on October 30, while delaying the REAX Engine track to Monday for an additional improvement pass. A chain-commitment limit meant hotkeys submitting competition entries could not also serve inference and were being deregistered during evaluation; the team introduced a keep-alive weight for entries that pass copy checks and beat the entry floor to prevent this. Some older entries scored before the rule change, including UID 111, were still pruned and had to be retroactively covered. The team also fixed a validator speed-measurement issue so hotkeys are credited at real throughput, removing the payout advantage of splitting one machine across multiple hotkeys, and set a 0.5 TAO minimum registration fee alongside the existing increase and cap.
- Community
- Miners questioned why UID105's incentive dropped despite high performance and raised concerns about hotkey deregistration during competition evaluation and the fairness of multi-hotkey versus multi-machine setups. After UID 111 was deregistered due to the keep-alive gap, a community member flagged it along with UID26 and UID27 losing emission.
- Official
- The team acknowledged the keep-alive gap affecting UID 111 and apologized, fixing it retroactively since 19:21 UTC, and confirmed step one of the speed-measurement fix went live at the 21:15 UTC weight set, with multi-machine support for a single hotkey planned next.
24h change +27.64%
- What happened
- SN92 (REAX) launched its decision-model mining network following a pilot partnership with msg group's CTO, and released the open-weight s1-llm-auto-router decision model for LLM routing served on REAX. The team introduced a new reward split (50% inference, 20% engine competition, 2x15% use-case competitions), replacing the initial all-inference distribution, and deployed a capacity-scoring v2 update so rewards scale with verified per-hotkey throughput. A delay in miner incentive, caused by root stake being attributed to UID 0 instead of the validator's child key, was fixed by making the validator the subnet owner hotkey. The registration fee cap was lowered to 0.3 TAO after the capacity fix, then reversed hours later to a 1.26x rising fee capped at 2 TAO after a registration rush.
- Community
- Miners debated whether running multiple hotkeys per GPU increases rewards and whether the lack of Sybil protection would turn registration into a UID race, while others pushed back on high registration fees. Community members also noted the subnet's launch tweet reaching over 500k views and ranking third among AI release announcements.
- Official
- The team announced the reward-split change, released capacity scoring v2, published open practice datasets on Hugging Face, and posted several updates addressing the incentive delay, a capacity probe bug, and registration fee adjustments.
24h change +511.29%
- What happened
- SN92 (REAX)'s channel, previously unclaimed, was claimed by a new operator who launched the DecisionModels project built on a REAX inference engine and opened mining. Mining launched in two parts, 80% model hosting and 20% competitions, with the first competition focused on speeding up the REAX engine. Miners initially reported zero incentive with 100% burn because the operator's validator had not yet become the lead validator on-chain. The operator later introduced an EU-GDPR-compliant mining tier requiring EU company registration and a written contract for enterprise hosting.
- Community
- For an extended period before the claim, members speculated about who controlled the unclaimed channel, with some stating as fact that a known figure directed it; a moderator repeatedly intervened to limit unverified claims. After the channel was claimed, members congratulated the new operator and asked about the project's purpose, mining access, and the burn/incentive issue.
- Official
- The operator clarified that their validator's child hotkey would activate the next day around 09:30 UTC, after which their larger stake weight would determine consensus and resolve the zero-incentive issue. The operator also described the EU-GDPR tier as a way to serve enterprise customers subject to European regulation and stated it is, to their knowledge, the first subnet to offer this.