Meanwhile, in our datacenter... You can fit more into your @MistralAI context window and let it work longer for the same price and quality. Now available for Mistral Large 4. Register: app.thesoma.ai/register
Bittensor subnet news
Subnet teams' own channels, X posts, press, newsletters and events read from the chain — GitHub lives in its own tab
Validator Astrid (5ELR…qwVh) scheduled a child-key change on 20 subnets
Validator hotkey 5ELREhApbCahM7FyGLM1V9WDsnnjCRmMCJTmtQD51oAEqwVh announced new child keys on SN6, SN8, SN9, SN20, SN21, SN44, SN47, SN53, SN54, SN61, SN65, SN73 and 8 more, applying at block 9,292,933 (~24h). Stake delegated to it there routes through its children after that.
Between blocks 9,285,716 and 9,285,779
SOMA SN114 puts a CPU budget around agent tests
Bittensor's SOMA SN114 changes how validators run agent tests, limiting resources and the CPU count shown to software that creates parallel workers.
Tao Outsidersource ↗

We have the best context compressor around! 🧵 1/4 SOMA can provide 30% more effective compute to your system. This gain has been measured against an unchanged baseline, with identical tasks, model, provider, environment and generation settings. thesoma.ai/labs/experiment-methodology
Linkthesoma.aithesoma.ai/labs/experiment-methodology🧵 4/4 We didn't stop at comparing SOMA against the baseline. We also benchmarked SOMA head-to-head against Caveman on a separate test set, using DeepSeek V4.1 Flash - the same model currently used in our competition. The result? SOMA delivers greater token savings AND a higher benchmark score.

🧵 3/4 We've benchmarked SOMA across 6 models, with token savings ranging from 18.91% to 47.10%, while maintaining comparable or better solve rates. We repeat runs because agent trajectories are stochastic: one run can be short while another loops, explores a dead end or hits provider noise. Repeating runs lets us distinguish stable improvements from lucky runs.

🧵 2/4 The basic truth is that every unnecessary token sent to a model consumes inference capacity. And so, removing unnecessary context translates into: - lower cost - lower model workload - higher throughput from the same hardware
We have the best context compressor around! 🧵 1/4 SOMA can provide 30% more effective compute to your system. This gain has been measured against an unchanged baseline, with identical tasks, model, provider, environment and generation settings. Check out the details: thesoma.ai/labs/experiment-methodology
Linkthesoma.aithesoma.ai/labs/experiment-methodologyValidator TAO.app (5CoZ…bifj) scheduled a child-key change on 125 subnets
Validator hotkey 5CoZxgtfhcJKX2HmkwnsN18KbaT9aih9eF3b6qVPTgAUbifj announced new child keys on SN1, SN2, SN3, SN4, SN5, SN6, SN7, SN8, SN9, SN10, SN11, SN12 and 113 more, applying at block 9,281,605 (~24h). Stake delegated to it there routes through its children after that.
Between blocks 9,274,365 and 9,274,433
SN114 large sell: 470.9 τ
SN114 large buy: 470.7 τ
Validator Tensorplex Labs (5E4z…ULde) scheduled a child-key change on 4 subnets
Validator hotkey 5E4z3h9yVhmQyCFWNbY9BPpwhx4xFiPwq3eeqmBgVF6KULde announced new child keys on SN102, SN109, SN114, SN121, applying at block 9,279,905 (~24h). Stake delegated to it there routes through its children after that.
Between blocks 9,272,702 and 9,272,768
Validator Tensorplex Labs (5E4z…ULde) re-scheduled a child-key change on 2 subnets
Validator hotkey 5E4z3h9yVhmQyCFWNbY9BPpwhx4xFiPwq3eeqmBgVF6KULde announced new child keys on SN109, SN114, applying at block 9,271,784 (~24h). Stake delegated to it there routes through its children after that. It replaces the changes that were pending on SN109 (block 9,265,725) and SN114 (block 9,266,128), which will not apply then.
Between blocks 9,264,527 and 9,264,589
Validator 5HK2…YYXr scheduled a child-key change on 2 subnets
Validator hotkey 5HK2LZRrvj581VjyxuFxb6ehFZoNi5PqAg3Y2HsmYPhGYYXr announced new child keys on SN109, SN114, applying at block 9,271,688 (~24h). Stake delegated to it there routes through its children after that.
Between blocks 9,264,465 and 9,264,527
Validator 5HK1…RJAK scheduled a child-key change on 2 subnets
Validator hotkey 5HK1Ubcg6MBwDGW7Td4RtAvE1FNyvkHvXKfwymW9q1BCRJAK announced new child keys on SN109, SN114, applying at block 9,271,685 (~24h). Stake delegated to it there routes through its children after that.
Between blocks 9,264,465 and 9,264,527
Validator Kiln (5F7d…r6LW) scheduled a child-key change on 2 subnets
Validator hotkey 5F7dvCS7mdzJU4o9bAUx4LPgpF3XeMM1XEz9nVqVNga9r6LW announced new child keys on SN109, SN114, applying at block 9,271,691 (~24h). Stake delegated to it there routes through its children after that.
Between blocks 9,264,465 and 9,264,527
Validator 5EqY…oaUf scheduled a child-key change on 2 subnets
Validator hotkey 5EqYdsxW1EYfb7PdJrazCYd1JuunqhABtHSWKh34jPbQoaUf announced new child keys on SN109, SN114, applying at block 9,271,694 (~24h). Stake delegated to it there routes through its children after that.
Between blocks 9,264,465 and 9,264,527
Validator Firepool (5Deo…zD9Y) scheduled a child-key change on 68 subnets
Validator hotkey 5Deo9Q3SnZWNPSEPRTgapbyy6egKu2oaNSqD4RQHHJEuzD9Y announced new child keys on SN4, SN6, SN8, SN9, SN15, SN16, SN17, SN19, SN21, SN23, SN27, SN29 and 56 more, applying at block 9,269,281 (~24h). Stake delegated to it there routes through its children after that.
Between blocks 9,262,073 and 9,262,137
Why is SOMA such a great compressor in the #Bittensor ecosystem? One reason is that it extends your context window by 20%, allowing you to run longer sessions without hitting limits. Shout-out to @infinitetensor and @_overment for the inspiration!
Validator Tensorplex Labs (5E4z…ULde) re-scheduled a child-key change on 8 subnets
Validator hotkey 5E4z3h9yVhmQyCFWNbY9BPpwhx4xFiPwq3eeqmBgVF6KULde announced new child keys on SN107, SN111, SN112, SN114, SN118, SN120, SN124, SN125, applying at block 9,266,119 (~24h). Stake delegated to it there routes through its children after that. It replaces the changes that were pending on SN107 (block 9,265,722), SN111 (block 9,265,695), SN112 (block 9,265,698), SN114 (block 9,265,680), SN118 (block 9,265,662), SN120 (block 9,265,668) and 2 more, which will not apply then.
Between blocks 9,258,916 and 9,258,981
Validator Tensorplex Labs (5E4z…ULde) scheduled a child-key change on 22 subnets
Validator hotkey 5E4z3h9yVhmQyCFWNbY9BPpwhx4xFiPwq3eeqmBgVF6KULde announced new child keys on SN98, SN99, SN100, SN101, SN102, SN104, SN110, SN111, SN112, SN113, SN114, SN115 and 10 more, applying at block 9,265,650 (~24h). Stake delegated to it there routes through its children after that. It replaces the changes that were pending on SN98 (block 9,265,320), SN99 (block 9,265,308), SN100 (block 9,265,323), SN101 (block 9,265,326), SN102 (block 9,265,329), SN104 (block 9,265,332) and 5 more, which will not apply then.
Between blocks 9,258,445 and 9,258,514
Novelty Search: youtube.com/watch?is=haU9XWqXlGvcHmK5&v=YJkzjES…
Linkyoutube.comyoutube.com/watch?is=haU9XWqXlGvcHmK5&v=YJkzjES67ro&feature=youtu.beValidator 5HK2…YYXr scheduled a child-key change on 3 subnets
Validator hotkey 5HK2LZRrvj581VjyxuFxb6ehFZoNi5PqAg3Y2HsmYPhGYYXr announced new child keys on SN44, SN102, SN114, applying at block 9,260,288 (~24h). Stake delegated to it there routes through its children after that.
Between blocks 9,253,039 and 9,253,107
Validator 5HK1…RJAK scheduled a child-key change on 3 subnets
Validator hotkey 5HK1Ubcg6MBwDGW7Td4RtAvE1FNyvkHvXKfwymW9q1BCRJAK announced new child keys on SN44, SN102, SN114, applying at block 9,260,285 (~24h). Stake delegated to it there routes through its children after that.
Between blocks 9,253,039 and 9,253,107
Validator Kiln (5F7d…r6LW) scheduled a child-key change on 3 subnets
Validator hotkey 5F7dvCS7mdzJU4o9bAUx4LPgpF3XeMM1XEz9nVqVNga9r6LW announced new child keys on SN44, SN102, SN114, applying at block 9,260,291 (~24h). Stake delegated to it there routes through its children after that.
Between blocks 9,253,039 and 9,253,107
Validator 5EqY…oaUf scheduled a child-key change on 3 subnets
Validator hotkey 5EqYdsxW1EYfb7PdJrazCYd1JuunqhABtHSWKh34jPbQoaUf announced new child keys on SN44, SN102, SN114, applying at block 9,260,294 (~24h). Stake delegated to it there routes through its children after that.
Between blocks 9,253,039 and 9,253,107
SOMA Highlights - October 9 We integrated SOMA with new inference providers: @chutes_ai, @say_gm_, and @engyai, and started proxing traffic to Albedo. We had a great time on @opentensor Novelty Search and @ExploitSummit. Check out the latest updates below. Compress. Pay less.
Validator 5HK2…YYXr scheduled a child-key change on SN114
Validator hotkey 5HK2LZRrvj581VjyxuFxb6ehFZoNi5PqAg3Y2HsmYPhGYYXr announced new child keys on SN114, applying at block 9,248,888 (~24h). Stake delegated to it there routes through its children after that.
Between blocks 9,241,642 and 9,241,704View subnet →
Validator 5HK1…RJAK scheduled a child-key change on SN114
Validator hotkey 5HK1Ubcg6MBwDGW7Td4RtAvE1FNyvkHvXKfwymW9q1BCRJAK announced new child keys on SN114, applying at block 9,248,885 (~24h). Stake delegated to it there routes through its children after that.
Between blocks 9,241,642 and 9,241,704View subnet →
Validator Kiln (5F7d…r6LW) scheduled a child-key change on SN114
Validator hotkey 5F7dvCS7mdzJU4o9bAUx4LPgpF3XeMM1XEz9nVqVNga9r6LW announced new child keys on SN114, applying at block 9,248,891 (~24h). Stake delegated to it there routes through its children after that.
Between blocks 9,241,642 and 9,241,704View subnet →