sudo_set_min_allowed_weights
Call v138 → current #14Sets the minimum number of weights a neuron must set on a subnet .
View calls on chainCall Workflow
This diagram shows the call execution flow: starting with sudo_set_min_allowed_weights, passing through validation
(signature, nonce, mortality, fee payment), then pre-dispatch checks, followed by dispatch and modifies storage: SubtensorModule.MinAllowedWeights, 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
Forces neurons to evaluate multiple peers rather than concentrating weights. Promotes network health.
Use Cases
- Encouraging weight distribution
- Preventing weight concentration
Input Parameters
Permissions
Origin
Root
Required Role
Requirements
- Caller is root or subnet owner
- Subnet exists
Effects
Storage Modified
Postconditions
- MinAllowedWeights updated
Side Effects
- Neurons must set at least this many weights
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_min_allowed_weights call
const netuid = 1;
const min_allowed_weights = 0;
const call = api.tx[stringCamelCase("AdminUtils")][stringCamelCase("sudo_set_min_allowed_weights")](
netuid,
min_allowed_weights
);Runtime Info
View Source- Pallet Index
- 19
- Call Index
- 14
- First Version
- v138
- Current Version
- v393