Call Workflow
This diagram shows the call execution flow: starting with kill_storage, passing through validation
(signature, nonce, mortality, fee payment), then pre-dispatch checks, followed by dispatch, 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: validatorsdevelopers
The Big Picture
Deletes specific storage keys. Used during migrations to clean up old storage.
Use Cases
- Remove obsolete storage
- Clean up after failed upgrades
From Chain Metadata
Kill some items from storage.
Input Parameters
| # | Name | Type | Description |
|---|---|---|---|
| 0 | keys | Vec<Vec<u8>> Vec | keys (Vec<Vec<u8>>) |
Permissions
Origin
Unknown
Required Role
Permission data inferred from metadata. May be incomplete.
Requirements
- Caller is root/sudo
- Valid storage keys
Effects
Postconditions
- Storage values deleted
- Keys return default values
Side Effects
- Can corrupt chain state
- Bypasses cleanup logic
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 });
// Build kill_storage call
const keys = 0;
const call = api.tx[stringCamelCase("System")][stringCamelCase("kill_storage")](
keys
);Runtime Info
- Pallet Index
- 0
- Call Index
- 5
- First Version
- v101
- Current Version
- v393