sudo_set_weights_version_key
Call v138 → current #6Sets the weights version key for a subnet .
View calls on chainCall Workflow
This diagram shows the call execution flow: starting with sudo_set_weights_version_key, passing through validation
(signature, nonce, mortality, fee payment), then pre-dispatch checks, followed by dispatch and modifies storage: SubtensorModule.WeightsVersionKey, 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
Version keys ensure miners use the expected weight format. Changing this can force upgrades across the subnet.
Use Cases
- Forcing weight format upgrades
- Deprecating old weight schemes
Input Parameters
Permissions
Origin
Root
Required Role
Requirements
- Caller is root or subnet owner
- Subnet exists
Effects
Storage Modified
Postconditions
- WeightsVersionKey updated
Side Effects
- Miners using old version key may have weights rejected
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_version_key call
const netuid = 1;
const weights_version_key = 0;
const call = api.tx[stringCamelCase("AdminUtils")][stringCamelCase("sudo_set_weights_version_key")](
netuid,
weights_version_key
);Runtime Info
View Source- Pallet Index
- 19
- Call Index
- 6
- First Version
- v138
- Current Version
- v393