sudo_set_bonds_penalty
Call v233 → current #60Sets the bonds penalty parameter for a subnet .
View calls on chainCall Workflow
This diagram shows the call execution flow: starting with sudo_set_bonds_penalty, passing through validation
(signature, nonce, mortality, fee payment), then pre-dispatch checks, followed by dispatch and modifies storage: SubtensorModule.BondsPenalty, 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
Penalties discourage validators from frequently changing their miner preferences. Promotes stability.
Use Cases
- Tuning bond incentives
- Discouraging bond manipulation
From Chain Metadata
The extrinsic sets the bonds penalty for a subnet. It is only callable by the root account or subnet owner. The extrinsic will call the Subtensor pallet to set the bonds penalty.
Input Parameters
Permissions
Origin
Root
Required Role
Permission data inferred from metadata. May be incomplete.
Requirements
- Caller is root or subnet owner
- Subnet exists
Effects
Storage Modified
Postconditions
- BondsPenalty updated
Side Effects
- Affects penalty for bond violations
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_bonds_penalty call
const netuid = 1;
const bonds_penalty = 0;
const call = api.tx[stringCamelCase("AdminUtils")][stringCamelCase("sudo_set_bonds_penalty")](
netuid,
bonds_penalty
);Runtime Info
View Source- Pallet Index
- 19
- Call Index
- 60
- First Version
- v233
- Current Version
- v393