sudo_set_tx_rate_limit
Call v138 → current #2Sets the transaction rate limit for the network.
View calls on chainCall Workflow
This diagram shows the call execution flow: starting with sudo_set_tx_rate_limit, passing through validation
(signature, nonce, mortality, fee payment), then pre-dispatch checks, followed by dispatch and modifies storage: SubtensorModule.TxRateLimit, 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: subnet owners
The Big Picture
Controls how many transactions an account can submit per interval. Higher limits increase throughput but may enable spam.
Use Cases
- Spam prevention tuning
- Network throughput adjustment
Input Parameters
| # | Name | Type | Description |
|---|---|---|---|
| 0 | tx_rate_limit | u64 | tx_rate_limit (u64) |
Permissions
Origin
Root
Required Role
Requirements
- Caller is root account
Effects
Storage Modified
Postconditions
- TxRateLimit updated
Side Effects
- Affects transaction throttling across network
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 sudo_set_tx_rate_limit call
const tx_rate_limit = 0;
const call = api.tx[stringCamelCase("AdminUtils")][stringCamelCase("sudo_set_tx_rate_limit")](
tx_rate_limit
);Runtime Info
View Source- Pallet Index
- 19
- Call Index
- 2
- First Version
- v138
- Current Version
- v393