sudo_set_lock_reduction_interval
Call v138 → current #38Sets how often subnet lock requirements decrease.
View calls on chainCall Workflow
This diagram shows the call execution flow: starting with sudo_set_lock_reduction_interval, passing through validation
(signature, nonce, mortality, fee payment), then pre-dispatch checks, followed by dispatch and modifies storage: SubtensorModule.NetworkLockReductionInterval, 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
Subnet locks decrease over time. This controls the reduction schedule.
Use Cases
- Tuning lock economics
- Encouraging long-term commitment
Input Parameters
| # | Name | Type | Description |
|---|---|---|---|
| 0 | interval | u64 | interval (u64) |
Permissions
Origin
Root
Required Role
Permission data inferred from metadata. May be incomplete.
Requirements
- Caller is root account
Effects
Storage Modified
Postconditions
- LockReductionInterval updated
Side Effects
- Affects how fast lock costs decrease over time
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_lock_reduction_interval call (typed, named args)
const interval = 0n;
const tx = api.tx.AdminUtils.sudo_set_lock_reduction_interval({
interval,
});Runtime Info
View Source- Pallet Index
- 19
- Call Index
- 38
- First Version
- v138
- Current Version
- v411