This call was removed in v127
This call is no longer available in the current runtime. Existed from v101 to v127. Shown here for historical reference.
sudo_add_network_connection_requirement
Call Removed v101 → v127 (removed) #12sudo_add_network_connection_requirement call from SubtensorModule pallet .
Call Workflow
This diagram shows the call execution flow: starting with sudo_add_network_connection_requirement, passing through validation
(signature, nonce, mortality, fee payment), then pre-dispatch checks where it may fail with errors like NetworkDoesNotExist, SubNetworkDoesNotExist, RootNetworkDoesNotExist, 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.
Input Parameters
Permissions
Origin
Unknown
Required Role
Permission data inferred from metadata. May be incomplete.
Requirements
- Required conditions for addition met
Effects
Postconditions
- Item successfully added/registered
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_add_network_connection_requirement call
const netuid_a = 1;
const netuid_b = 1;
const requirement = 0;
const call = api.tx[stringCamelCase("SubtensorModule")][stringCamelCase("sudo_add_network_connection_requirement")](
netuid_a,
netuid_b,
requirement
);Runtime Info
View Source- Pallet Index
- 7
- Call Index
- 12
- First Version
- v101
- Removed In
- v127