swap_authorities
Call v138 → current #0Replaces Aura consensus authorities with new validator set.
View calls on chainCall Workflow
This diagram shows the call execution flow: starting with swap_authorities, 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.
Used by: subnet owners
The Big Picture
This is a critical governance call that changes who produces blocks. Used during network upgrades or emergency situations where the validator set must be replaced immediately.
Use Cases
- Emergency validator rotation
- Scheduled authority changes
- Network upgrades requiring new validators
Input Parameters
| # | Name | Type | Description |
|---|---|---|---|
| 0 | new_authorities | BoundedVec | new_authorities (BoundedVec) |
Permissions
Origin
Root
Required Role
Requirements
- Caller is root account
- Valid authority list provided
Effects
Postconditions
- Aura authorities updated to new set
- Block production shifts to new validators
Side Effects
- Existing validators lose block production rights
- Network consensus mechanism updates
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 swap_authorities call
const new_authorities = 0 as any /* BoundedVec */;
const call = api.tx[stringCamelCase("AdminUtils")][stringCamelCase("swap_authorities")](
new_authorities
);Runtime Info
View Source- Pallet Index
- 19
- Call Index
- 0
- First Version
- v138
- Current Version
- v393