Call Workflow
This diagram shows the call execution flow: starting with disable_lp, passing through validation
(signature, nonce, mortality, fee payment), then pre-dispatch checks, followed by dispatch which emits events: UserLiquidityToggled and modifies storage: EnabledUserLiquidity, 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: developers
The Big Picture
Emergency brake - stops new positions while allowing existing LPs to exit.
Use Cases
- Emergency shutdown
- Critical maintenance pause
From Chain Metadata
Disable user liquidity in all subnets. Emits `Event::UserLiquidityToggled` on success
This call takes no parameters.
Permissions
Origin
Unknown
Required Role
Permission data inferred from metadata. May be incomplete.
Requirements
- Caller has sudo/admin privileges
Effects
Events Emitted
Storage Modified
Postconditions
- All subnets have user liquidity disabled
- Existing positions remain
Side Effects
- Emits UserLiquidityToggled for each subnet
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 disable_lp call (no parameters)
const call = api.tx[stringCamelCase("Swap")][stringCamelCase("disable_lp")]();Runtime Info
View Source- Pallet Index
- 28
- Call Index
- 5
- First Version
- v350
- Current Version
- v393