sudo_set_commit_reveal_version
Call v301 → current #71Sets the commit-reveal version for weight submission.
View calls on chainCall Workflow
This diagram shows the call execution flow: starting with sudo_set_commit_reveal_version, passing through validation
(signature, nonce, mortality, fee payment), then pre-dispatch checks, followed by dispatch and modifies storage: SubtensorModule.CommitRevealWeightsVersion, 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 control for commit-reveal protocol. Allows upgrading the mechanism while maintaining compatibility.
Use Cases
- Protocol upgrades
- Forcing commit-reveal format changes
From Chain Metadata
Sets the commit-reveal weights version for all subnets
Input Parameters
| # | Name | Type | Description |
|---|---|---|---|
| 0 | version | u16 | version (u16) |
Permissions
Origin
Root
Required Role
Permission data inferred from metadata. May be incomplete.
Requirements
- Caller is root account
Effects
Storage Modified
Postconditions
- CommitRevealVersion updated
Side Effects
- May require miners to update their weight submission code
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_commit_reveal_version call
const version = 0;
const call = api.tx[stringCamelCase("AdminUtils")][stringCamelCase("sudo_set_commit_reveal_version")](
version
);Runtime Info
View Source- Pallet Index
- 19
- Call Index
- 71
- First Version
- v301
- Current Version
- v393