Starting take rate for child key relationships.
Current Value
0Relevant for: validatorsdeveloperssubnet owners
The Big Picture
Child keys allow hotkeys to delegate operations to sub-keys. When emissions flow to a child key, the parent takes a commission. This constant sets the default commission for new child key relationships. It's like delegation but for operational keys rather than stake.
Why This Matters
If you're setting up child key infrastructure, this is your starting commission rate. Child key arrangements let you distribute operations while maintaining economic control.
Example
With InitialDefaultChildKeyTake of 1000 (10%), when a child key earns 1 TAO, 0.1 TAO goes to the parent key and 0.9 TAO goes to the child. You can adjust this after setup.
Common Questions
- What's a child key used for?
- Operational separation. Run multiple miners under one parent, delegate specific subnet operations, or create organizational hierarchies.
- Can I change child key take later?
- Yes, subject to rate limits. Like delegate take, changes may be constrained to prevent gaming.
From Chain Metadata
Initial default childkey take.
Use Cases
- Child key setup
- Take calculations
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 InitialDefaultChildKeyTake constant
const value = await api.constants.SubtensorModule.InitialDefaultChildKeyTake();
console.log("InitialDefaultChildKeyTake:", value);Type Information
- Type
- u16
- Byte Size
- 2 bytes
- Encoding
- fixed
- Raw Hex
- 0x0000
Runtime Info
- Pallet
- SubtensorModule
- First Version
- v195
- Latest Version
- v195
- Current Runtime
- v411