Limits frequency of child take modifications.
Current Value
216000Relevant for: validatorsdevelopers
The Big Picture
Like delegate take, child key take can't be changed rapidly. This protects child key operators from sudden parent take increases. The rate limit creates predictability in parent-child economic relationships and builds trust in the arrangement.
Why This Matters
If you're a parent or child key operator, know you're locked into take rates for the rate limit period. Negotiate carefully before establishing the relationship.
Example
With TxChildKeyTakeRateLimit of 7200 blocks, parent take changes are locked for ~24 hours. A child key operator has a day to respond to any take increase by the parent.
Common Questions
- Can parents and children negotiate different terms?
- The chain enforces standard rate limits. Off-chain agreements are possible but the chain limits apply to actual take changes.
- What happens if I violate the rate limit?
- The transaction fails. The previous take rate remains in effect until the rate limit period expires.
From Chain Metadata
Initial childkey take transaction rate limit.
Use Cases
- Child key management
- Rate limiting
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 InitialTxChildKeyTakeRateLimit constant
const value = api.consts[stringCamelCase("SubtensorModule")][stringCamelCase("InitialTxChildKeyTakeRateLimit")];
console.log("InitialTxChildKeyTakeRateLimit:", value.toHuman());
// Convert RAO to TAO if this is a balance value
const taoValue = value.toBigInt() / BigInt(1e9);
console.log("TAO:", taoValue.toString());Type Information
- Type
- u64
- Byte Size
- 8 bytes
- Encoding
- fixed
- Raw Hex
- 0xc04b030000000000
Runtime Info
- Pallet
- SubtensorModule
- First Version
- v195
- Latest Version
- v195
- Current Runtime
- v393