sudo_set_network_pow_registration_allowed
Call v138 → current #20Enables or disables POW-based registration on a subnet .
View calls on chainCall Workflow
This diagram shows the call execution flow: starting with sudo_set_network_pow_registration_allowed, passing through validation
(signature, nonce, mortality, fee payment), then pre-dispatch checks where it may fail with errors like NetworkDoesNotExist, followed by dispatch and modifies storage: SubtensorModule.NetworkPowRegistrationAllowed, 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
Controls whether proof-of-work registration is allowed. Subnets can require burn-only registration.
Use Cases
- Switching to burn-only registration
- Emergency POW disable
Input Parameters
Permissions
Origin
Root
Required Role
Requirements
- Caller is root or subnet owner
- Subnet exists
Effects
Storage Modified
Postconditions
- POW registration flag updated
Side Effects
- Affects which registration methods are available
Possible Errors
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_network_pow_registration_allowed call
const netuid = 1;
const registration_allowed = true;
const call = api.tx[stringCamelCase("AdminUtils")][stringCamelCase("sudo_set_network_pow_registration_allowed")](
netuid,
registration_allowed
);Runtime Info
View Source- Pallet Index
- 19
- Call Index
- 20
- First Version
- v138
- Current Version
- v393