sudo_set_owner_hparam_rate_limit
Call v320 → current #75Sets how often subnet owners can change hyperparameters .
View calls on chainCall Workflow
This diagram shows the call execution flow: starting with sudo_set_owner_hparam_rate_limit, passing through validation
(signature, nonce, mortality, fee payment), then pre-dispatch checks, followed by dispatch and modifies storage: SubtensorModule.OwnerHyperparamRateLimit, 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
Prevents subnet owners from rapidly changing parameters, which could destabilize their subnet.
Use Cases
- Preventing rapid parameter changes
- Stability guarantees
From Chain Metadata
Sets the owner hyperparameter rate limit in epochs (global multiplier). Only callable by root.
Input Parameters
| # | Name | Type | Description |
|---|---|---|---|
| 0 | epochs | u16 | epochs (u16) |
Permissions
Origin
Root
Required Role
Permission data inferred from metadata. May be incomplete.
Requirements
- Caller is root account
Effects
Storage Modified
Postconditions
- OwnerHparamRateLimit updated
Side Effects
- Limits owner hyperparameter change frequency
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_owner_hparam_rate_limit call
const epochs = 0;
const call = api.tx[stringCamelCase("AdminUtils")][stringCamelCase("sudo_set_owner_hparam_rate_limit")](
epochs
);Runtime Info
View Source- Pallet Index
- 19
- Call Index
- 75
- First Version
- v320
- Current Version
- v393