sudo_set_mechanism_count
Call v320 → current #76Sets the number of mechanisms for a subnet .
View calls on chainCall Workflow
This diagram shows the call execution flow: starting with sudo_set_mechanism_count, passing through validation
(signature, nonce, mortality, fee payment), then pre-dispatch checks, followed by dispatch and modifies storage: SubtensorModule.MechanismCountCurrent, 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
Some subnets can have multiple consensus mechanisms. This controls the count.
Use Cases
- Multi-mechanism subnets
- Advanced subnet configuration
From Chain Metadata
Sets the desired number of mechanisms in a subnet
Input Parameters
Permissions
Origin
Root
Required Role
Permission data inferred from metadata. May be incomplete.
Requirements
- Caller is root or subnet owner
- Subnet exists
Effects
Storage Modified
Postconditions
- MechanismCount updated
Side Effects
- Affects subnet's mechanism configuration
Code Examples
import { createClient, Binary } from "polkadot-api";
import { getWsProvider } from "polkadot-api/ws";
import { sub } from "@polkadot-api/descriptors"; // generated by: npx papi add sub -w wss://entrypoint-finney.opentensor.ai:443
const client = createClient(getWsProvider("wss://entrypoint-finney.opentensor.ai:443"));
const api = client.getTypedApi(sub);
// Build sudo_set_mechanism_count call (typed, named args)
const netuid = 1;
const mechanism_count = 0;
const tx = api.tx.AdminUtils.sudo_set_mechanism_count({
netuid,
mechanism_count,
});Runtime Info
View Source- Pallet Index
- 19
- Call Index
- 76
- First Version
- v320
- Current Version
- v411