PerpetualLockUpdated
Event v411 → v422, v423 → v424, v432 → v440, v441 → current #140Emitted when a coldkey 's perpetual-lock flag flips on or off for a specific subnet .
View events on chainUseful for: stakerssubnet ownersanalytics
The Big Picture
Perpetual flag changes are a strong commitment signal. Aggregating these tells you how much of the locked supply has opted out of decay entirely.
Use Cases
- Track perpetual-lock adoption per subnet
- Identify accounts committed to long-term subnet positions
From Chain Metadata
A coldkey's perpetual lock flag was updated.
Migration Notes
v424 v432 Breaking
netuid changed from u16 to NetUid
Update decoders: SCALE encoding is positional, so any signature change (added, removed, or type-changed fields, or storage shape changes) shifts byte offsets and existing decoders will misparse this item. Re-derive types from the new metadata.
Triggers
Preconditions
- set_perpetual_lock call succeeded
Effects
Postconditions
- DecayingLock entry inserted (enabled=false) or removed (enabled=true)
Side Effects
- The coldkey's individual lock either stops decaying (perpetual) or resumes normal decay
Event Data
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);
// Subscribe to PerpetualLockUpdated events
client.finalizedBlock$.subscribe(async (block) => {
const events = await api.event.SubtensorModule.PerpetualLockUpdated.get(block.hash);
for (const evt of events) {
console.log("PerpetualLockUpdated:", evt.payload);
}
});Version History
v411 block 8,283,784 3 args
v423 block 8,486,593 3 args
v432 block 8,636,190 3 args
v441 block 8,765,683 3 args Current
Runtime Info
View Source- Pallet Index
- 7
- Event Index
- 140
- First Version
- v411
- Current Version
- v472