RevealPeriodEpochs

Storage Map v205 → current

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	key1	u16	key1 (u16)

Stored Value

u64

Value in RAO (÷10⁹ for TAO)

RAO -> TAO (/ 10^9)

Code Examples

import { ApiPromise, WsProvider } from "@polkadot/api";
import { stringCamelCase } from "@polkadot/util";

const provider = new WsProvider("wss://entrypoint-finney.opentensor.ai:443");
const api = await ApiPromise.create({ provider });

// Query RevealPeriodEpochs storage
const key1 = 0;

const result = await api.query
  [stringCamelCase("SubtensorModule")]
  [stringCamelCase("RevealPeriodEpochs")](
  key1
);

console.log("RevealPeriodEpochs:", result.toHuman());

Runtime Info

View Source

Pallet: SubtensorModule
Storage Kind: Map
First Version: v205
Current Version: v393

Back to SubtensorModule Storage