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

tx_childkey_take_rate_limit (u64)

RAO -> TAO (/ 10^9)

Relationships

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

Runtime Info

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