This call was removed in v326
This call is no longer available in the current runtime. Existed from v123 to v326. Shown here for historical reference.
change_key
Call Removed v123 → v326 (removed) #4Changes a Senate member's account key.
Call Workflow
This diagram shows the call execution flow: starting with change_key, passing through validation
(signature, nonce, mortality, fee payment), then pre-dispatch checks, followed by dispatch which emits events: KeyChanged, 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: validators
The Big Picture
Security without losing membership.
Use Cases
- Key rotation
From Chain Metadata
Swap out the sending member for some other key `new`. May only be called from `Signed` origin of a current member. Prime membership is passed from the origin account to `new`, if extant.
Input Parameters
| # | Name | Type | Description |
|---|---|---|---|
| 0 | new | MultiAddress | new (MultiAddress) |
Permissions
Origin
Unknown
Required Role
Permission data inferred from metadata. May be incomplete.
Requirements
- Origin is member
Effects
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 change_key call
const new = 0 as any /* MultiAddress */;
const call = api.tx[stringCamelCase("SenateMembers")][stringCamelCase("change_key")](
new
);Runtime Info
- Pallet Index
- 10
- Call Index
- 4
- First Version
- v123
- Removed In
- v326