LastAdjustmentBlock
Storage Map v101 → v411Block of last difficulty /burn adjustment per subnet .
Explore chainQueried by: minersdevelopersanalytics
The Big Picture
Registration difficulty and burn costs adjust periodically. This tracks when the last adjustment occurred. Combined with AdjustmentInterval, you can predict next changes.
Use Cases
- Calculate time until next adjustment
- Monitor adjustment frequency
- Plan registration timing
From Chain Metadata
MAP ( netuid ) --> Block at last adjustment.
Purpose & Usage
Purpose
Track when registration costs were last adjusted.
Common Query Patterns
- Query by netuid
Query Keys
| # | Name | Type | Description |
|---|---|---|---|
| 1 | netuid | u16 | netuid (u16, hashed key component) |
Stored Value
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);
// Query LastAdjustmentBlock storage
const netuid = 1;
const result = await api.query.SubtensorModule.LastAdjustmentBlock.getValue(netuid);
console.log("LastAdjustmentBlock:", result);Version History
v101 block 1 Added
v123 block 720,235 Internal re-bind
v149 block 3,014,339 Internal re-bind
v166–v194 · runtime versions skipped on chain (never deployed)
v195 block 3,791,350 Internal re-bind
v278–v289 · runtime versions skipped on chain (never deployed)
v290 block 5,947,548 Internal re-bind Current
Runtime Info
View Source- Pallet
- SubtensorModule
- Storage Kind
- Map
- First Version
- v101
- Current Version
- v411