sudo_set_bonds_reset_enabled
Call v290 → current #70Enables or disables bonds reset capability on a subnet .
View calls on chainCall Workflow
This diagram shows the call execution flow: starting with sudo_set_bonds_reset_enabled, passing through validation
(signature, nonce, mortality, fee payment), then pre-dispatch checks, followed by dispatch which emits events: BondsResetToggled and modifies storage: SubtensorModule.BondsResetOn, 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
Bond resets can clear stuck validator-miner relationships. This controls whether that option is available.
Use Cases
- Allowing bond resets
- Emergency recovery options
From Chain Metadata
Enables or disables Bonds Reset for a given subnet.
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
Events Emitted
Storage Modified
Postconditions
- BondsResetEnabled flag updated
- BondsResetToggled event emitted
Side Effects
- Affects whether bonds can be reset
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_reset_enabled call
const netuid = 1;
const enabled = true;
const call = api.tx[stringCamelCase("AdminUtils")][stringCamelCase("sudo_set_bonds_reset_enabled")](
netuid,
enabled
);Runtime Info
View Source- Pallet Index
- 19
- Call Index
- 70
- First Version
- v290
- Current Version
- v393