This call was removed in v306
This call is no longer available in the current runtime. Existed from v233 to v306. Shown here for historical reference.
set_rate_limit
Call Removed v233 → v306 (removed) #1Sudo-set the commitment rate limit
Call Workflow
This diagram shows the call execution flow: starting with set_rate_limit, 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
Sudo-set the commitment rate limit
Input Parameters
| # | Name | Type | Description |
|---|---|---|---|
| 0 | rate_limit_blocks | u32 | rate_limit_blocks (u32) |
Permissions
Origin
Unknown
Required Role
Permission data inferred from metadata. May be incomplete.
Requirements
- Caller authorized to make changes
Effects
Postconditions
- Value successfully updated
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_rate_limit call
const rate_limit_blocks = 0;
const call = api.tx[stringCamelCase("Commitments")][stringCamelCase("set_rate_limit")](
rate_limit_blocks
);Runtime Info
View Source- Pallet Index
- 18
- Call Index
- 1
- First Version
- v233
- Removed In
- v306