sudo_set_max_mechanism_count
Call v385 → current #88Sets the global maximum number of mechanisms in a subnet
View calls on chainCall Workflow
This diagram shows the call execution flow: starting with sudo_set_max_mechanism_count, passing through validation
(signature, nonce, mortality, fee payment), then pre-dispatch checks, followed by dispatch, 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.
From Chain Metadata
Sets the global maximum number of mechanisms in a subnet
Input Parameters
| # | Name | Type | Description |
|---|---|---|---|
| 0 | max_mechanism_count | u8 MechId | max_mechanism_count: Mechanism identifier |
Permissions
Origin
Root
Required Role
Permission data inferred from metadata. May be incomplete.
Requirements
- Caller authorized to make changes
Effects
Postconditions
- Value successfully updated
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_max_mechanism_count call (typed, named args)
const max_mechanism_count = 0;
const tx = api.tx.AdminUtils.sudo_set_max_mechanism_count({
max_mechanism_count,
});Runtime Info
View Source- Pallet Index
- 19
- Call Index
- 88
- First Version
- v385
- Current Version
- v411