RevealPeriodEpochs

Storage Map v205 → v411

Epochs allowed for weight reveal after commit.

Queried by: validatorsdevelopers

The Big Picture

In commit-reveal, committed weights must be revealed within this many epochs. After the window, unrevealed commits expire.

Use Cases

Check reveal deadline
Plan weight submission timing
Build commit-reveal tools

From Chain Metadata

Map (netuid) --> Number of epochs allowed for commit reveal periods

Purpose & Usage

Purpose

Define reveal window for commit-reveal.

Common Query Patterns

Query by netuid

Part of: Commit-Reveal Weights (CRV3)

Query Keys

#	Name	Type	Description
1	netuid	u16	netuid (u16, hashed key component)

Stored Value

u64

Number (u64)

RAO -> TAO (/ 10^9)

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 RevealPeriodEpochs storage
const netuid = 1;

const result = await api.query.SubtensorModule.RevealPeriodEpochs.getValue(netuid);
console.log("RevealPeriodEpochs:", result);

Version History

Version:

v205 block 4,209,446 Added

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: v205
Current Version: v411

Back to SubtensorModule Storage