Subnet 73: Parked
Subnet 73 is a Bittensor subnet slot whose current live Finney identity is registered as “Parked.” The identity does not currently list a public GitHub repository, website, contact address, description, logo, or additional project metadata.
Because no public source repository or project documentation is named in the live identity, this page treats Subnet 73 as a parked slot rather than as an active public protocol with reproducible miner and validator behavior. Readers should verify the live chain identity before relying on this page, because subnet operators can update identity fields over time.
What Parked Provides
The useful fact about Subnet 73 is its registered status. The live identity name is “Parked,” and the other public metadata fields are blank. There is therefore no source-backed public task, application, or service to describe beyond the subnet’s current on-chain identity.
This is different from active subnets that publish implementation repositories, product websites, or technical documentation. If Subnet 73 later receives a public repository or description, those live identity fields should become the starting point for a new source-backed article revision.
Miner and Validator Roles
No source-backed miner or validator roles can be described from the current identity. The live identity does not publish an implementation repository, docs, or task description that would explain how miners perform work or how validators evaluate that work.
In active subnets, miner and validator behavior is usually documented by the subnet’s public materials and then converted into weights processed through Yuma Consensus. For Subnet 73, the safe reference point is the general Mining and Validating model, not a subnet-specific mechanism.
On-Chain Identity
Readers can reproduce the live identity fields with the Bittensor CLI command documented in the
btcli reference:
btcli subnets get-identity --netuid 73 --network finney.
That Finney identity reports the subnet name as “Parked.” The GitHub repository, contact, subnet URL, description, logo, and additional fields are currently blank.
Relationship to Yuma Consensus
Subnet 73 is registered on Bittensor and would use 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 73’s current identity is registered as “Parked” with no public task or implementation 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 73 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 73, 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 73 is registered as the live production subnet at netuid 73. 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 73 should not be read as generic Bittensor subnet documentation, a description of an active public protocol, or an endorsement of any specific off-chain project. Its live identity is registered as Parked with no public repository, website, contact, or task description, so Taopedia cannot source miner and validator behavior beyond the generic Bittensor role model.
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 (btcli reference).
If a real repository or mechanism spec is later registered on-chain, that registered source should replace third-party summaries as the basis for a revised, source-backed article. Until then, any claim about Subnet 73’s specific scoring logic or task output would be speculative.
Validator weights still flow through Yuma Consensus to determine emissions each tempo (Yuma Consensus, Emission).