Beam is Bittensor subnet 105 (SN105), a project in the Storage and Data Availability lane. Decentralized bandwidth for the machine internet.
Bandwidth is the internet's forgotten resource. Compute has Bittensor, storage has Filecoin, but moving data efficiently between systems remains controlled by a handful of cloud giants. Beam is building the open coordination layer for that missing piece.
It is an educational deep dive, not a recommendation to stake. For live price, pool depth, and performance, always open the live subnet page.
What is Beam (SN105)?
Beam is a decentralized bandwidth network on Bittensor that coordinates data transfers across distributed infrastructure. It lets anyone contribute bandwidth capacity and get rewarded based on how well they actually perform, verified through a mechanism called Proof-of-Bandwidth.
In plain English: It's like a decentralized Cloudflare for data movement, where anyone with spare bandwidth can participate and earn by reliably moving data between systems.
Centralized reference points: Cloudflare, AWS Transfer Family, Fastly
How miners and validators work
Like every Bittensor subnet, SN105 is a two-sided market: miners produce work, validators score it, and emissions follow those weights under the network’s dTAO economics.
- Validators read Proof-of-Bandwidth records generated by each transfer and set weights based on verified throughput, latency, and reliability
Mechanism and design
According to the Beam GitHub repository and website, transfers flow through a three-tier architecture. Clients submit transfer requests to BeamCore (the central coordination layer). BeamCore assigns chunks to orchestrators by stake-weighted allocation. Orchestrators then coordinate workers via WebSocket, who fetch data from source and deliver to destinations. Each completed transfer generates a Proof-of-Bandwidth record. Validators read those proofs from BeamCore and use them to set weights on-chain, determining which orchestrators receive emissions.
Supported transfer patterns include single-to-single, fan-out (one source, multiple destinations), aggregation (multiple sources, one destination), and full mesh. Beam integrates with AWS S3, Google Cloud, Cloudflare R2, Snowflake, REST APIs, Webhooks, and MCP servers according to the project website.
The chain buy rate of 0.81% reflects active market demand coming alongside emissions, and the price is up over 196% in 30 days, suggesting a strong recent staking inflow. Emission share sits at around 1.24%, with a root proportion of 0.40, meaning organic staking makes up the majority of the pool.
Why the project exists
- The problem it solves: Global bandwidth capacity exists across data centers, ISPs, and independent operators but remains economically fragmented. There's no open market for it.
- The opportunity: AI pipelines, agentic workflows, and cross-cloud synchronization move enormous volumes of data. That demand is growing fast, with no open alternative to centralized CDNs.
- The Bittensor advantage: Performance-based rewards aligned to actual delivery metrics, not self-reported capacity. Any operator can join without a commercial contract.
- Traction signals: The website reports aggregate bandwidth of 847 Gb/s, 2.4 PB volume, and 1,247 miners as of the time of writing. The GitHub repo was updated in April 2026, and the subnet holds 7 active miners.
What stakers should check before buying alpha
Subnet storytelling is cheap. On-chain and product checks are not. Use the same framework as our subnet metrics guide:
| Check | Why |
|---|---|
| Real product / docs / repo | Separates shipping teams from narrative-only slots |
| Pool depth (TAO) | Your exit door: thin pools amplify slippage |
| Net flows (7d / 30d) | Under flow-based emissions, capital votes with its feet |
| Emission share | Whether the market is funding this subnet right now |
| Ownership concentration | Large holders can move a small alpha market |
| Immunity / deregistration | Post-immunity weak slots can lose the race (see immunity guide) |
Pull the live numbers on Beam · SN105 rather than trusting any static screenshot in a blog post.
Risk factors
- Execution: Only 7 active miners on the network. The infrastructure exists but real-world transfer volume is not independently verifiable from chain data alone.
- Centralization in BeamCore: The architecture relies on BeamCore as the coordination layer. If this is a centralized service, it introduces a single point of failure the README does not fully address.
- Competition: Decentralized bandwidth is a well-funded space (Filecoin, Storj, Akash). Beam's differentiation is its Bittensor-native performance incentives, but market positioning is still early.
- Liquidity: Market cap around 14,700 TAO with thin supply. Large exits would move the price significantly.
How this fits a TAO portfolio
Many holders keep a root vs subnet split: root for calmer TAO exposure, subnets like Beam for thematic upside (and higher variance). If you use TaoScale, you can size SN105 from your wallet without handing over custody. See non-custodial staking.
- Live market: SN105 on TaoScale
- Browse and stake: /invest
- More subnet explainers: /blog/subnets
FAQ
What does Beam do on Bittensor?
It's like a decentralized Cloudflare for data movement, where anyone with spare bandwidth can participate and earn by reliably moving data between systems.
What is the SN105 alpha token?
When you stake TAO into subnet 105, you receive that subnet’s alpha. Its price versus TAO moves with the subnet’s pool (see what is dTAO).
How do I research Beam before staking?
Read the mechanism above, open the official repo/docs when available, then verify pool depth, flows, and activity on SN105. Cross-check with the metrics checklist.
Is this financial advice?
No. TaoScale publishes educational explainers and live tools. Decisions to stake are yours alone.
Not financial advice. Educational overview of Beam (SN105) compiled from public project materials and ecosystem documentation. Mechanisms and market structure change, so verify live data and official sources before acting.
