Queried by: validatorssubnet ownersdevelopers
The Big Picture
Subnets can use different consensus mechanisms. This identifies which mechanism is active on each subnet.
Use Cases
- Check subnet mechanism type
- Build mechanism-aware tools
- Research subnet configurations
From Chain Metadata
MAP ( netuid ) --> subnet mechanism
Purpose & Usage
Purpose
Track which mechanism each subnet uses.
Common Query Patterns
- Query by netuid
Query Keys
| # | Name | Type | Description |
|---|---|---|---|
| 1 | netuid | u16 | netuid (u16, hashed key component) |
Stored Value
subnet (u16)
Relationships
Modified By
Related Events
Code Examples
import { createClient, Binary } from "polkadot-api";
import { getWsProvider } from "polkadot-api/ws";
import { sub } from "@polkadot-api/descriptors"; // generated by: npx papi add sub -w wss://entrypoint-finney.opentensor.ai:443
const client = createClient(getWsProvider("wss://entrypoint-finney.opentensor.ai:443"));
const api = client.getTypedApi(sub);
// Query SubnetMechanism storage
const netuid = 1;
const result = await api.query.SubtensorModule.SubnetMechanism.getValue(netuid);
console.log("SubnetMechanism:", result);Version History
v233 block 4,920,350 Added
v253–v256 · runtime versions skipped on chain (never deployed)
v257 block 5,228,683 Internal re-bind
v278–v289 · runtime versions skipped on chain (never deployed)
v290 block 5,947,548 Internal re-bind Current
Runtime Info
View Source- Pallet
- SubtensorModule
- Storage Kind
- Map
- First Version
- v233
- Current Version
- v411