DeletionQueueCounter
Storage Plain v334 → v411 Changed in v411Counter for the deletion queue.
Explore chainQueried by: developers
The Big Picture
Bookkeeping for the incremental deletion mechanism.
Use Cases
- Monitor deletion queue health
From Chain Metadata
A pair of monotonic counters used to track the latest contract marked for deletion and the latest deleted contract in queue.
Purpose & Usage
Purpose
Tracks position in the deletion queue for efficient processing.
Common Query Patterns
- Query for queue state
Stored Value
value (DeletionQueueManager)
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 DeletionQueueCounter storage (no keys - plain value)
const result = await api.query.Contracts.DeletionQueueCounter.getValue();
console.log("DeletionQueueCounter:", result);Version History
v334 block 6,811,690 Added
v353–v360 · runtime versions skipped on chain (never deployed)
v361 block 7,063,679 Internal re-bind
v363–v364 · runtime versions skipped on chain (never deployed)
v365 block 7,135,419 Internal re-bind
v378–v384 · runtime versions skipped on chain (never deployed)
v385 block 7,782,670 Internal re-bind
v386–v390 · runtime versions skipped on chain (never deployed)
v391 block 7,782,857 Internal re-bind
v394–v400 · runtime versions skipped on chain (never deployed)
v401 block 8,036,576 Internal re-bind
v403–v410 · runtime versions skipped on chain (never deployed)
v411 block 8,283,784 Internal re-bind Current
Runtime Info
- Pallet
- Contracts
- Storage Kind
- Plain
- First Version
- v334
- Current Version
- v411