CommitRevealWeightsEnabled
Storage Map v151 → v411Whether commit-reveal weights is enabled per subnet .
Explore chainQueried by: validatorssubnet ownersdevelopers
The Big Picture
Commit-reveal prevents weight copying by requiring validators to commit weights before seeing others. When enabled, weights must go through the commit-reveal cycle rather than being set directly.
Use Cases
- Check if commit-reveal is required before setting weights
- Monitor subnet weight policies
- Build weight submission tools
From Chain Metadata
MAP ( netuid ) --> commit reveal v2 weights are enabled
Purpose & Usage
Purpose
Toggle commit-reveal mechanism for weight setting.
Common Query Patterns
- Query by netuid
Query Keys
| # | Name | Type | Description |
|---|---|---|---|
| 1 | netuid | u16 | netuid (u16, hashed key component) |
Stored Value
commit (bool)
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 CommitRevealWeightsEnabled storage
const netuid = 1;
const result = await api.query.SubtensorModule.CommitRevealWeightsEnabled.getValue(netuid);
console.log("CommitRevealWeightsEnabled:", result);Version History
v151 block 3,157,274 Added
v166–v194 · runtime versions skipped on chain (never deployed)
v195 block 3,791,350 Internal re-bind
v213–v215 · runtime versions skipped on chain (never deployed)
v216 block 4,510,996 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
- v151
- Current Version
- v411