poke_deposit
Call v320 → current #10Update proxy deposit amounts based on current parameters.
View calls on chainCall Workflow
This diagram shows the call execution flow: starting with poke_deposit, passing through validation
(signature, nonce, mortality, fee payment), then pre-dispatch checks, followed by dispatch which emits events: DepositPoked and modifies storage: Proxies, 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: stakersvalidatorsdevelopers
The Big Picture
Recalculate deposits after chain parameter changes.
Use Cases
- Recover excess deposit after parameter changes
From Chain Metadata
Poke / Adjust deposits made for proxies and announcements based on current values. This can be used by accounts to possibly lower their locked amount. The dispatch origin for this call must be _Signed_. The transaction fee is waived if the deposit amount has changed. Emits `DepositPoked` if successful.
This call takes no parameters.
Permissions
Origin
Signed
Required Role
Permission data inferred from metadata. May be incomplete.
Requirements
- Caller has proxy or announcement deposits
Effects
Events Emitted
Storage Modified
Postconditions
- Deposits adjusted
- DepositPoked event emitted
Side Effects
- Balance may change
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 poke_deposit call (no parameters)
const call = api.tx[stringCamelCase("Proxy")][stringCamelCase("poke_deposit")]();Runtime Info
- Pallet Index
- 16
- Call Index
- 10
- First Version
- v320
- Current Version
- v393