Subnet 110: Green Compute
Green Compute is Bittensor Subnet 110. Its on-chain identity describes the subnet as enterprise inference hardware powered by 100% green energy and lists green-compute.com as the subnet URL. The live identity does not currently publish a GitHub repository.
What Green Compute Provides
Green Compute presents itself as a decentralized GPU-compute marketplace on Bittensor. The website describes users renting GPUs, running OpenAI-compatible inference, and using verified-green compute capacity. It also names Bittensor subnet 110 as the network layer for the marketplace.
The public product framing is specific to inference and hardware supply. The site references RTX 4090 and RTX 5090 hardware, metered inference, enterprise buyers, and compute providers that contribute renewable-powered GPU sites. It also describes hardware-location proofs and green-energy verification as requirements for miner participation.
Miner and Validator Roles
Miners are hardware providers. In Green Compute’s public materials, they contribute GPU capacity from renewable-powered sites and are evaluated around whether their hardware and power source meet the subnet’s verification requirements. The site states that verified green nodes receive emission priority and that hardware-location proofs are part of the participation model.
Validators score miner-provided compute. The website describes validators as checking miner work against inference demand and verification requirements before payouts. Those scores become subnet weights that feed into Yuma Consensus, which converts validator agreement into Bittensor incentives.
On-Chain Identity
Live SN110 data is available on TaoStats. The live Finney identity for netuid 110 reports the subnet name as Green Compute, the subnet URL as green-compute.com, and the description as “Enterprise Inference Hardware, 100% Green Energy.” The GitHub, contact, and Discord fields are currently blank.
Relationship to Yuma Consensus
Subnet 110 uses Yuma Consensus to convert validator weight vectors into the emission shares distributed to miners and validators within the subnet each tempo. The linked documentation describes how validator weight submissions are aggregated into consensus weights for each miner registered on the subnet.
Green Compute’s on-chain identity lists a project website URL but no GitHub repository. No public source provides a source-verified description of how validators score miners on Subnet 110 beyond what the registered identity fields contain. The Emission documentation describes how consensus weights determine each participant’s share of the subnet’s accumulated emission each tempo.
Development Stage Context
The Introduction to Bittensor describes subnet development as moving from localnet to testnet and then mainnet. For Green Compute (SN110), that sequence applies to the standard Bittensor lifecycle: localnet for isolated development, testnet for shared non-production testing, and mainnet for live operation with real emissions.
On mainnet, Green Compute (SN110) is registered as the live production subnet at netuid 110. The Bittensor Networks reference separates mainnet, testnet, and localnet. Participation examples or emission outcomes from one environment should not be read as representing production subnet performance in another environment.
Reader Boundary
Subnet 110 Green Compute should not be read as a fully open-source subnet with published scoring code on GitHub. Live Finney identity lists green-compute.com but leaves GitHub, contact, and Discord fields blank, so mechanism detail beyond the registered identity and public website should be treated carefully.
Public Site Describes Inference Supply, Not Generic Compute
The Green Compute website presents a decentralized GPU marketplace focused on OpenAI-compatible inference, named hardware such as RTX 4090 and RTX 5090, and enterprise buyers renting metered capacity. Generic GPU workloads or unverified power claims should not be assumed to map onto the subnet without matching the site’s stated verification model.
Verified Green Nodes and Location Proofs
The same public materials describe hardware-location proofs and green-energy verification as miner participation requirements and state that verified green nodes receive emission priority. Those claims come from the project website rather than a linked public repository README, so they should be read as published product boundaries rather than independently audited implementation detail.
Validator weights still flow through Yuma Consensus to determine emissions each tempo (Yuma Consensus, Emission).