Into:TensorClaw
Real traffic, real rewards
As of · Jun 4, 10:37 UTC
LLM inference on Bittensor, but rewards go to whoever actually processes real API traffic, not whoever passes the cleanest benchmark.
What is TensorClaw
TensorClaw is a Bittensor (SN92) designed to aggregate language model API nodes globally and serve them through a single, load-balanced endpoint. connect their LLM endpoints or cloud API access to TensorClaw's routing layer, and score them on how much real traffic they actually process.
The simple version: It's like OpenRouter, but decentralized. Competing miners serve API requests, and the ones processing the most traffic earn the most rewards.
Centralized equivalent: OpenRouter, Together.ai, or the OpenAI API itself. TensorClaw aims to offer the same aggregated API surface with decentralized incentives replacing the subscription model.
How it works:
- Miners connect to a central WebSocket router (AICenter) as pure clients, exposing their LLM backend without needing a public IP, port forwarding, or DDoS protection
- Validators fire real 5-token micro-prompts at each miner to verify they're alive, then score them primarily based on actual commercial API token throughput over a rolling 24-hour window
Why This Matters
- The problem it solves: LLM inference APIs are dominated by a few large providers. There's no competitive market forcing quality improvements or cost efficiency at the infrastructure level.
- The opportunity: Developer and enterprise demand for reliable, aggregated LLM API access is large and growing. A subnet that routes real traffic to the highest-performing nodes at any moment has a clear utility case.
- The Bittensor advantage: The incentive design directly links miner rewards to commercial output. According to the GitHub repository, 90% of a miner's score comes from actual token throughput. Miners who serve real traffic get paid more. Miners who just pass synthetic probes get almost nothing.
- Traction signals: The subnet is in early stage. On-chain data shows no active miners registered at this time, and miner-side are currently going unclaimed. The WebSocket infrastructure, scoring system, and deployment guides are described as complete in the GitHub repository.
Other research from the same neighborhood of the network.