Subnet 92: wgmi
wgmi is Bittensor Subnet 92. Its on-chain identity is registered under the name wgmi. All other public identity fields — project URL, GitHub repository, Discord, and description — are blank.
Because the on-chain identity does not list a project URL, GitHub repository, Discord, or description, this article does not describe the miner task, scoring function, or operator workflow for Subnet 92.
On-Chain Identity
The verified chain facts for netuid 92 are: the registered identity name is wgmi; URL, GitHub, Discord, and description fields are all empty. Live SN92 data is available on TaoStats.
Relationship to Yuma Consensus
Subnet 92 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 no source-backed on-chain identity URL or GitHub repo is available for Subnet 92, 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 92 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 92, 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 92 is registered as the live production subnet at netuid 92. 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.
Miner and Validator Roles
Subnet 92 operates under the standard Bittensor two-role structure. Miners supply the subnet’s capability and validators evaluate those contributions and set weights. Reward distribution follows Yuma Consensus.
Reader Boundary
Subnet 92 should not be read as generic Bittensor subnet documentation, an active public protocol description, or proof of a reproducible miner task on netuid 92. Its live Finney identity registers the name wgmi with blank URL, GitHub, Discord, and description fields, so Taopedia cannot source miner and validator behavior beyond the generic Bittensor role model (btcli reference).
Blank Identity Fields Block Mechanism Claims
Readers should treat this page as identity-state reporting and verify the current on-chain identity before relying on any description, because subnet operators can update identity fields over time. Until a real repository or mechanism spec is registered on-chain, statements about Subnet 92’s specific scoring logic or task output would be speculative.
The wgmi Name Is Not a Protocol Description
The registered subnet name is an on-chain label, not a substitute for README or website documentation. If a future operator registers project links and a mechanism description, that registered source should replace placeholder summaries as the basis for a revised article.
Validator weights still flow through Yuma Consensus to determine emissions each tempo (Yuma Consensus, Emission).