NetworkLockCostReductionIntervalSet
Event Re-added v134 → v135, v136 → v141, v142 → v148, v149 → v165, v195 → v219, v233 → v247, v252 → v265, v273 → v277, v290 → v315, v320 → v326, v334 → v367, v372 → current #61Emitted when lock cost reduction interval is changed.
View events on chainThe Big Picture
After high-demand periods, subnet lock costs should decrease toward the minimum. This interval controls how quickly that happens. Shorter intervals mean faster cost reduction (quicker return to baseline). Longer intervals mean costs stay elevated longer after demand spikes.
Why This Matters
If lock costs spiked due to high demand, understanding the reduction interval helps you decide whether to wait or act now. Faster reduction means cheaper costs soon. Slower reduction means waiting may not help much - costs stay elevated longer.
Example Scenario
Lock cost reduction was happening every 1000 blocks. To smooth out cost volatility, they increase the interval to 5000 blocks. NetworkLockCostReductionIntervalSet fires. Now lock costs decrease more slowly after spikes - less volatile but costs stay higher longer.
Common Questions
- How much does cost reduce per interval?
- Depends on the reduction algorithm. Check the specific reduction step parameter. The interval is WHEN it happens; the step is HOW MUCH.
- Can I predict when costs will reach minimum?
- Roughly. Track current cost, reduction interval, and reduction step. Extrapolate when cost will hit NetworkMinLockCost. But new demand can spike costs again.
- What if demand stays high?
- Costs stay elevated. Reduction happens when demand drops. If demand remains high, costs won't decrease even with intervals passing.
Use Cases
- Track lock cost reduction dynamics
- Plan optimal timing for subnet creation
- Monitor network economic tuning
- Build cost prediction tools
How to Use This Event
- → Track reduction interval for cost timing optimization
- → Monitor economic policy changes
- → Build cost decay prediction models
From Chain Metadata
the lock cost reduction is set
Triggers
Preconditions
- Caller has admin/sudo privileges
Effects
Postconditions
- NetworkLockReductionInterval updated
Side Effects
- Affects how quickly lock costs decrease
Event Data
| # | Name | Type | Description |
|---|---|---|---|
| 0 | arg0 | u64 | Event field #0 (u64) |
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 });
// Subscribe to NetworkLockCostReductionIntervalSet events
api.query.system.events((events) => {
events
.filter(({ event }) =>
event.section === stringCamelCase("SubtensorModule") &&
event.method === "NetworkLockCostReductionIntervalSet"
)
.forEach(({ event }) => {
console.log("NetworkLockCostReductionIntervalSet:", event.data.toHuman());
});
});Version History
Runtime Info
View Source- Pallet Index
- 7
- Event Index
- 61
- First Version
- v134
- Current Version
- v393