sudo_set_alpha_sigmoid_steepness
Call Re-added v273 → v277, v290 → current #68Sets the sigmoid steepness for alpha calculations.
View calls on chainCall Workflow
This diagram shows the call execution flow: starting with sudo_set_alpha_sigmoid_steepness, passing through validation
(signature, nonce, mortality, fee payment), then pre-dispatch checks, followed by dispatch and modifies storage: SubtensorModule.AlphaSigmoidSteepness, 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
The sigmoid function shapes how alpha values map. Steepness controls how sharp the transition is.
Use Cases
- Tuning alpha token curves
- Adjusting price sensitivity
Input Parameters
Permissions
Origin
Root
Required Role
Permission data inferred from metadata. May be incomplete.
Requirements
- Caller is root or subnet owner
- Subnet exists
- Value is positive
Effects
Storage Modified
Postconditions
- SigmoidSteepness updated
Side Effects
- Affects alpha curve shape
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_alpha_sigmoid_steepness call
const netuid = 1;
const steepness = 0;
const call = api.tx[stringCamelCase("AdminUtils")][stringCamelCase("sudo_set_alpha_sigmoid_steepness")](
netuid,
steepness
);Version History
v273 block 5,659,032 2 args
v290 block 5,947,548 2 args Current
Runtime Info
View Source- Pallet Index
- 19
- Call Index
- 68
- First Version
- v273
- Current Version
- v393