TxChildkeyTakeRateLimit

Storage Plain v195 → current

Rate limit for childkey take changes.

Explore chain
Queried by: validatorsdevelopers

The Big Picture

Childkey take changes are rate-limited to prevent gaming. This defines the minimum blocks between take changes.

Use Cases

  • Plan take change timing
  • Understand rate limits
  • Build take management tools

From Chain Metadata

ITEM ( tx_childkey_take_rate_limit )

Purpose & Usage

Purpose

Control frequency of childkey take modifications.

Common Query Patterns

  • Single value query

Stored Value

u64

Value in RAO (÷10⁹ for TAO)

RAO -> TAO (/ 10^9)

Relationships

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 TxChildkeyTakeRateLimit storage (no keys - plain value)
const result = await api.query
  [stringCamelCase("SubtensorModule")]
  [stringCamelCase("TxChildkeyTakeRateLimit")]();
console.log("TxChildkeyTakeRateLimit:", result.toHuman());

Runtime Info

View Source
Pallet
SubtensorModule
Storage Kind
Plain
First Version
v195
Current Version
v393
Back to SubtensorModule Storage