Subnet 104: For Sale
Subnet 104 is a Bittensor subnet slot whose current on-chain identity is registered as “for sale (burn to uid1).” Its description says the subnet is for sale and that, in the meantime, experimentation stops while the subnet is parked until sold. The identity does not currently list a public GitHub repository, website, contact address, Discord, logo, or additional project metadata.
Current Status
The useful fact about Subnet 104 is its registered status, not a project implementation. Unlike active subnets with public miner or validator repositories, Subnet 104’s live identity does not publish a source repository or project documentation. Readers should therefore treat it as a parked slot rather than as an active public protocol with reproducible miner and validator behavior.
The phrase “burn to uid1” is part of the registered identity text. This page does not interpret that phrase beyond the published identity fields, which present the subnet as parked until sold. Any future buyer or operator could update the identity fields and public materials, so readers should verify the live chain identity before relying on this page.
On-Chain Identity
Live SN104 data is available on TaoStats. The live Finney identity for netuid 104 reports the subnet name as “for sale (burn to uid1)” and the description as “subnet for sale. in the meantime, burning to uid1 and experimentation stops to park subnet until sold.” The GitHub, contact, URL, Discord, logo, and additional fields are currently blank.
Relationship to Yuma Consensus
Subnet 104 is registered on Bittensor and uses Yuma Consensus to convert validator weight vectors into the emission shares distributed to miners and validators within the subnet each tempo. The Yuma Consensus documentation describes how validator weight submissions are aggregated into consensus weights for each miner registered on the subnet.
Because Subnet 104’s live Finney identity registers the subnet as parked and for sale with no public GitHub repository, no source-backed description of how validators score miners or what weight vectors represent is available. The Emission documentation describes how consensus weights determine each participant’s share of the subnet’s accumulated emission each tempo, and those mechanics apply to Subnet 104 once a source-backed incentive mechanism is established.
Development Stage Context
The Introduction to Bittensor describes subnet development as moving from localnet to testnet and then mainnet. For Subnet 104, 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, Subnet 104 is registered as the live production subnet at netuid 104. 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 104 should not be read as generic Bittensor subnet documentation, an active public protocol description, or proof of a reproducible miner task on netuid 104. Its live Finney identity registers the subnet as for sale with experimentation stopped and blank GitHub, URL, Discord, and contact fields, so Taopedia cannot source miner and validator behavior beyond the generic Bittensor role model (btcli reference).
Parked-for-Sale Identity Is Not a Mechanism Spec
The registered description presents the subnet as parked until sold rather than as a documented miner task, validator workflow, or scoring rule set. Readers should verify the current on-chain identity before relying on any description, because a future buyer could replace the for-sale registration with new project metadata and documentation.
Identity Phrases Should Not Be Over-Interpreted
This page reports the published identity text, including the for-sale and burn-to-uid1 wording, without extending it into operational claims Taopedia cannot source. Until a real repository or mechanism description is registered on-chain, statements about Subnet 104’s specific weight logic or task output would be speculative.
Validator weights still flow through Yuma Consensus to determine emissions each tempo (Yuma Consensus, Emission).