set_heap_pages
Call v101 → current #1Set the number of WASM heap pages (root only).
View calls on chainCall Workflow
This diagram shows the call execution flow: starting with set_heap_pages, 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.
From Chain Metadata
Set the number of pages in the WebAssembly environment's heap.
Input Parameters
| # | Name | Type | Description |
|---|---|---|---|
| 0 | pages | u64 | pages (u64) |
Permissions
Origin
Unknown
Required Role
Permission data inferred from metadata. May be incomplete.
Requirements
- Caller is root/sudo
- Valid page count
Effects
Postconditions
- Heap pages configuration updated
Side Effects
- Affects WASM execution memory
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 set_heap_pages call
const pages = 0;
const call = api.tx[stringCamelCase("System")][stringCamelCase("set_heap_pages")](
pages
);Runtime Info
- Pallet Index
- 0
- Call Index
- 1
- First Version
- v101
- Current Version
- v393