Call Workflow
This diagram shows the call execution flow: starting with unnote_preimage, passing through validation
(signature, nonce, mortality, fee payment), then pre-dispatch checks, followed by dispatch which emits events: Noted, Cleared and modifies storage: PreimageFor, StatusFor, 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
Returns deposit for unused preimage.
Use Cases
- Reclaim deposit
From Chain Metadata
Clear an unrequested preimage from the runtime storage. If `len` is provided, then it will be a much cheaper operation. `hash`: The hash of the preimage to be removed from the store. `len`: The length of the preimage of `hash`.
Input Parameters
| # | Name | Type | Description |
|---|---|---|---|
| 0 | hash | H256 | hash (H256) |
Permissions
Origin
Unknown
Required Role
Permission data inferred from metadata. May be incomplete.
Requirements
- Preimage exists
- Not requested
- Caller is depositor
Effects
Storage Modified
Postconditions
- Preimage removed
- Deposit returned
Side Effects
- Emits Cleared
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 unnote_preimage call
const hash = 0 as any /* H256 */;
const call = api.tx[stringCamelCase("Preimage")][stringCamelCase("unnote_preimage")](
hash
);Runtime Info
- Pallet Index
- 14
- Call Index
- 1
- First Version
- v133
- Current Version
- v393