sudo_set_target_registrations_per_interval
Call v138 → current #21Sets the target registration rate for difficulty adjustment.
View calls on chainCall Workflow
This diagram shows the call execution flow: starting with sudo_set_target_registrations_per_interval, passing through validation
(signature, nonce, mortality, fee payment), then pre-dispatch checks, followed by dispatch and modifies storage: SubtensorModule.TargetRegistrationsPerInterval, 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 difficulty algorithm tries to achieve this many registrations per interval. Higher targets mean easier registration.
Use Cases
- Controlling subnet growth rate
- Balancing accessibility vs exclusivity
Input Parameters
Permissions
Origin
Root
Required Role
Requirements
- Caller is root or subnet owner
- Subnet exists
Effects
Storage Modified
Postconditions
- TargetRegistrationsPerInterval updated
Side Effects
- Difficulty will adjust toward this registration rate
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_target_registrations_per_interval call
const netuid = 1;
const target_registrations_per_interval = 0;
const call = api.tx[stringCamelCase("AdminUtils")][stringCamelCase("sudo_set_target_registrations_per_interval")](
netuid,
target_registrations_per_interval
);Runtime Info
View Source- Pallet Index
- 19
- Call Index
- 21
- First Version
- v138
- Current Version
- v393