sudo_set_weights_set_rate_limit
Call v138 → current #7Sets how often neurons can update weights on a subnet .
View calls on chainCall Workflow
This diagram shows the call execution flow: starting with sudo_set_weights_set_rate_limit, passing through validation
(signature, nonce, mortality, fee payment), then pre-dispatch checks, followed by dispatch and modifies storage: SubtensorModule.WeightsSetRateLimit, and finally post-dispatch where ExtrinsicSuccess is emitted and fees are settled.
Press enter or space to select a node. You can then use the arrow keys to move the node around. Press delete to remove it and escape to cancel.
Press enter or space to select an edge. You can then press delete to remove it or escape to cancel.
Click items to navigate. Pan and zoom to explore.
Used by: subnet owners
The Big Picture
Limits how frequently neurons can change their weight assignments. Lower values mean more responsive but noisier consensus.
Use Cases
- Controlling weight churn
- Stabilizing consensus
Input Parameters
Permissions
Origin
Root
Required Role
Requirements
- Caller is root or subnet owner
- Subnet exists
Effects
Storage Modified
Postconditions
- WeightsSetRateLimit updated
Side Effects
- Affects weight update frequency for all neurons
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 });
// Build sudo_set_weights_set_rate_limit call
const netuid = 1;
const weights_set_rate_limit = 0;
const call = api.tx[stringCamelCase("AdminUtils")][stringCamelCase("sudo_set_weights_set_rate_limit")](
netuid,
weights_set_rate_limit
);Runtime Info
View Source- Pallet Index
- 19
- Call Index
- 7
- First Version
- v138
- Current Version
- v393