Queried by: validatorsdelegatorsdevelopersanalytics
The Big Picture
Validators can't charge below this rate. This prevents a race to bottom where validators undercut each other to zero, making validation unsustainable. Ensures all validators have minimum compensation for their work.
Why This Matters
Want to attract delegators with 0% take? You can't go that low. The minimum ensures validators are compensated and can sustain operations.
Example Scenario
Query MinDelegateTake() returns 500 (5%). All validators must charge at least 5% take. Setting lower will fail.
Common Questions
- Why have a minimum?
- Prevents unsustainable validator operations. Running a validator costs money - hardware, bandwidth, monitoring. Zero take would attract delegators but bankrupt validators.
- Does this hurt delegators?
- Slightly higher fees, but ensures validators remain operational. A collapsed validator benefits no one.
Use Cases
- Check minimum required take when becoming a delegate
- Build UI sliders with correct min bounds
- Understand validator compensation floors
- Research delegation market dynamics
- Analyze validator economics
Purpose & Usage
Purpose
Floor on delegate fees to prevent race to bottom - ensures validator sustainability.
Common Query Patterns
- Single value query
- Verify take rate is within bounds
- Build take rate pickers with correct limits
Notes
- Value is in basis points
Stored Value
value (u16)
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 MinDelegateTake storage (no keys - plain value)
const result = await api.query
[stringCamelCase("SubtensorModule")]
[stringCamelCase("MinDelegateTake")]();
console.log("MinDelegateTake:", result.toHuman());Runtime Info
View Source- Pallet
- SubtensorModule
- Storage Kind
- Plain
- First Version
- v195
- Current Version
- v393