Floor on child key commission.
Current Value
0Relevant for: validatorsdevelopers
The Big Picture
Like MinDelegateTake, this sets a floor on child key commission. Parents cannot set zero take on child keys, ensuring some economic relationship remains. This prevents abuse scenarios where child keys are effectively independent but claim parent benefits.
Why This Matters
When configuring child key relationships, you cannot go below this commission. Plan your child key structure knowing this is the minimum economic tie.
Example
With MinChildKeyTake of 500 (5%), parent keys must take at least 5% from child key earnings. A parent cannot set 0% take to make the child fully independent economically.
Common Questions
- Why require minimum take?
- Child keys inherit some parent reputation/status. Minimum take ensures parents have skin in the game for child behavior.
- Can the minimum be 0?
- Check current runtime. If 0 is allowed, child keys can be effectively independent. If non-zero, parents always maintain some economic stake.
From Chain Metadata
Initial minimum childkey take.
Use Cases
- Child key validation
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 InitialMinChildKeyTake constant
const value = api.consts[stringCamelCase("SubtensorModule")][stringCamelCase("InitialMinChildKeyTake")];
console.log("InitialMinChildKeyTake:", value.toHuman());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
- v393