PendingChildKeys
Storage Map v216 → v411Scheduled child key changes awaiting execution.
Explore chainThe Big Picture
Child key changes don't execute immediately - they're scheduled with a delay for security. PendingChildKeys shows what changes are queued and when they'll take effect.
Why This Matters
Changed your child keys but nothing happened? Changes are pending. This shows what's scheduled and lets you verify or cancel before execution.
Example Scenario
Query PendingChildKeys(parent=hotkey_X, netuid=1) returns scheduled changes - new children, proportion changes, or removals that will execute after the delay period.
Common Questions
- Why the delay?
- Security. If someone compromises your key and changes child relationships, the delay gives you time to notice and respond.
- Can I cancel pending changes?
- Typically yes - submit new changes to override pending ones before execution.
Use Cases
- Check if you have pending child key changes
- Verify scheduled changes before execution
- Build child key management dashboards
- Monitor for unexpected configuration changes
- Track child key relationship updates
From Chain Metadata
DMAP ( netuid, parent ) --> (Vec<(proportion,child)>, cool_down_block)
Purpose & Usage
Purpose
Track pending child key modifications - changes go through a delay for security.
Common Query Patterns
- Query pending changes for a parent
- Check if child key changes are scheduled
- Monitor for upcoming configuration changes
Query Keys
Stored Value
- .0 pending_children — List of pending (proportion, child) pairs scheduled to take effect after cool_down_block. proportion is a u64 scaled to u64::MAX (sum to u64::MAX = 100%).
- .1 cool_down_block — Block number at which the pending child-key set is allowed to be applied. Acts as a rate-limit / dispute window.
Relationships
Modified By
Related Events
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 PendingChildKeys storage
const key1 = 0;
const key2 = "5GrwvaEF5zXb26Fz9rcQpDWS57CtERHpNehXCPcNoHGKutQY";
const result = await api.query.SubtensorModule.PendingChildKeys.getValue(key1, key2);
console.log("PendingChildKeys:", result);On-Chain Activity
10K–100K estimated writes
#47 most written storage item
Modified via user-submitted extrinsics
As of block 7,429,232
Version History
Runtime Info
View Source- Pallet
- SubtensorModule
- Storage Kind
- Map
- First Version
- v216
- Current Version
- v411