SUBNET TRACKER · All subnets
SN105 · Beam
Every Bittensor Daily mention of SN105 Beam, newest first. Price changes are snapshots from each edition.
24h change −3.58%
- What happened
- A miner alleged that an orchestrator used a paid transfer of $50 inside 'rooms' to bypass the Prism mechanism, with the work ending up concentrated among only five orchestrators. The team said it would look into the issue. Separately, the team confirmed it had optimized 1TB transfer speeds, cutting transfer time from over 50 minutes to under 4 minutes, which temporarily disrupted some miners' tier rankings.
- Community
- Several miners argued paid transfers let money buy Prism scores and higher tiers regardless of actual performance, while others maintained the ranking system reflects genuine performance and that paid transfers are not inherently unfair. Some miners reported being stuck in lower tiers for an extended period and said they were considering stopping.
- Official
- The team said it will look into the reported room exploit and acknowledged the recent transfer-speed optimization temporarily affected miners' tier positions.
24h change −2.31%
- What happened
- Miners in the SN105 (Beam) channel reported that room-transfer tasks were repeatedly going to a small set of orchestrators (around 12-15) at short, recurring intervals, with one miner citing data showing 2,714 of 2,847 chunks from a batch of transfers going to just 15 orchestrators. After an investigation, BeamCore confirmed the flagged room transfers are excluded as self-dealing and said the anti self-dealing system in PRISM is being upgraded, with new room-transfer test scenarios planned. Separately, the team declined to restore full historical dashboard and telemetry data publicly, citing the risk that competitors could train on it. Beam also reported moving 1TB of data in 2 minutes 42 seconds, 20% faster than last month, while running 2.5x more security checks.
- Community
- Miners repeatedly questioned why the same small set of orchestrators kept receiving the room-transfer tasks and asked the team to explain or exclude the request; some also pushed for public dashboard data so miners could spot anomalies themselves. The team asked miners to stop tagging staff and to file bug reports instead of repeating accusations.
- Official
- BeamCore confirmed the flagged room transfers are excluded as self-dealing, said the anti self-dealing system is being upgraded, and announced new room-transfer test scenarios covering all eligible orchestrators as a time-limited optimization campaign.
24h change −0.81%
- What happened
- On SN105 (Beam), a miner reported that sell-debt had appeared on a hotkey with zero recorded sales. Separately, a miner described a dispute over room-transfer eligibility, saying another operator's agent added delay to competing transfers and that requests from that operator's room consisted largely of hotkeys it controlled itself. The team confirmed that adaptive transfer limits and managed room lanes, which adjust parallel transfer capacity per destination based on delivery history, have been live since October 24.
- Community
- The miner who raised the sell-debt question asked for an explanation of how the debt was calculated. The miner raising the room-transfer concern asked the team how the current eligibility gate could detect the described pattern and whether delayed responses from a customized agent could be identified.
- Official
- The team said connection limits will become Beam-managed and that the eligibility gate needs more reference transfers to work at full capacity, adding that excluding such transfers is the anti-cheat system's responsibility. It also announced the adaptive transfer limits and managed room lanes update, live since October 24.
Read the full edition: SN15 (ORO) Bans 32 Accounts After Spend-Limit Manipulation Audit →
24h change −2.45%
- What happened
- On SN105 (Beam), a miner raised concerns about the fairness and transparency of room-transfer eligibility, questioning why some requests were approved while others were not. Other miners argued that the paid room-transfer economics could let capital outweigh engineering skill in determining emissions. Separately, a miner built and demonstrated a live video and audio streaming proof-of-concept over Beam's messaging protocol, running it through a Discord-hosted room-viewer tool.
- Community
- Miners debated the allocation dispute at length, with one pointing to the publicly available assignment-plan data showing allocation tied to PRISM scores, while others continued to question the broader incentive design. Separately, miners discussed creating a dedicated community group to help increase Beam's visibility.
- Official
- The team stated that streaming and message protocols are currently excluded from PRISM scoring, so miners can test without penalty, and offered an unlimited API key for streaming cost testing. The team also praised the miner's streaming demo.
24h change −2.15%
- What happened
- Miners on SN105 (Beam) identified an apparent self-transfer exploit in which transfers show files already present at the destination, allowing unusually fast completions (one case cited at 2140 Mbps, ~400ms) that bypass genuine upload verification; one miner reported records suggesting roughly 100 UIDs involved across multiple groups. Separately, a validator-pointed benchmark destination (172.232.226.191:9000) was reported unstable, refusing connections and causing legitimate transfers from honest miners to fail, triggering 3x PRISM penalties and rank drops from Tier D to Tier E for some participants. The team temporarily raised Beam transfer pricing to $15 per TB as a short-term measure tied to the miner-owned transfer issue. Orchestrator operators also continued to report recurring NATS authentication-expired errors.
- Community
- Miners shared transfer IDs and timing data to document the exploit and debated whether it could be explained by legitimate caching, with one miner noting the etag used to verify uploads can be generated locally without an actual upload. A miner proposed an 'accredited account' system so only vetted customer traffic counts toward incentive, as a way to curb wash trading without banning accounts. Separately, miners affected by the unstable benchmark endpoint asked the team to filter or blacklist destinations that drop connections, and others troubleshot the NATS auth errors by rebuilding against the latest commit and matching API keys.
- Official
- The team stated the self-transfer exploit "is not tolerated and will be punished," with further information to come, and said a separate issue with stuck sell-allowance debt would be addressed separately. It also announced a temporary increase in transfer pricing to $15 per TB while the miner-owned transfer issue is addressed, calling the adjustment short-term.