sudo_set_owner_immune_neuron_limit
Call v306 → current #72Sets how many neurons subnet owners can make immune.
View calls on chainCall Workflow
This diagram shows the call execution flow: starting with sudo_set_owner_immune_neuron_limit, passing through validation
(signature, nonce, mortality, fee payment), then pre-dispatch checks, followed by dispatch and modifies storage: SubtensorModule.ImmuneOwnerUidsLimit, 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
Subnet owners can grant immunity to some neurons. This limits how many to prevent abuse.
Use Cases
- Controlling owner privileges
- Limiting immunity abuse
From Chain Metadata
Sets the number of immune owner neurons
Input Parameters
Permissions
Origin
Root
Required Role
Permission data inferred from metadata. May be incomplete.
Requirements
- Caller is root or subnet owner
- Subnet exists
Effects
Storage Modified
Postconditions
- OwnerImmuneNeuronLimit updated
Side Effects
- Affects owner's ability to protect neurons
Code Examples
import { createClient, Binary } from "polkadot-api";
import { getWsProvider } from "polkadot-api/ws";
import { sub } from "@polkadot-api/descriptors"; // generated by: npx papi add sub -w wss://entrypoint-finney.opentensor.ai:443
const client = createClient(getWsProvider("wss://entrypoint-finney.opentensor.ai:443"));
const api = client.getTypedApi(sub);
// Build sudo_set_owner_immune_neuron_limit call (typed, named args)
const netuid = 1;
const immune_neurons = 0;
const tx = api.tx.AdminUtils.sudo_set_owner_immune_neuron_limit({
netuid,
immune_neurons,
});Runtime Info
View Source- Pallet Index
- 19
- Call Index
- 72
- First Version
- v306
- Current Version
- v411