This call was removed in v306
This call is no longer available in the current runtime. Existed from v195 to v306. Shown here for historical reference.
sudo_set_network_max_stake
Call Removed v195 → v306 (removed) #53Sets the maximum stake allowed for a specific network.
Call Workflow
This diagram shows the call execution flow: starting with sudo_set_network_max_stake, passing through validation
(signature, nonce, mortality, fee payment), then pre-dispatch checks where it may fail with errors like NetworkDoesNotExist, 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 maximum stake allowed for a specific network. This function allows the root account to set the maximum stake for a given network. It updates the network's maximum stake value and logs the change.
Input Parameters
Permissions
Origin
Root
Required Role
Permission data inferred from metadata. May be incomplete.
Requirements
- Caller authorized to make changes
- Sufficient balance for staking operation
Effects
Postconditions
- Value successfully updated
- Stake updated successfully
Possible Errors
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_network_max_stake call
const netuid = 1;
const max_stake = 1_000_000_000n;
const call = api.tx[stringCamelCase("AdminUtils")][stringCamelCase("sudo_set_network_max_stake")](
netuid,
max_stake
);Runtime Info
View Source- Pallet Index
- 19
- Call Index
- 53
- First Version
- v195
- Removed In
- v306