sudo_set_max_allowed_validators

Call v138 → v277, v290 → current #25

Sets the maximum number of validators allowed on a subnet .

View calls on chain

Click items to navigate. Pan and zoom to explore.

Used by: subnet owners

The Big Picture

Not all neurons are validators. This caps how many can participate in consensus on this subnet.

Use Cases

  • Controlling validator count
  • Balancing decentralization vs efficiency

From Chain Metadata

The extrinsic sets the maximum allowed validators for a subnet. It is only callable by the root account. The extrinsic will call the Subtensor pallet to set the maximum allowed validators.

Input Parameters

#NameTypeDescription
0
netuid
u16 NetUidnetuid: Subnet ID (u16, 0-65535)
1
max_allowed_validators
u16 max_allowed_validators (u16)

Permissions

Origin
Root
Required Role

Requirements

  • Caller is root or subnet owner
  • Subnet exists
  • Value <= max_allowed_uids

Effects

Storage Modified

Postconditions

  • MaxAllowedValidators updated

Side Effects

  • Affects how many neurons can be validators

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_max_allowed_validators call (typed, named args)
const netuid = 1;
const max_allowed_validators = 0;

const tx = api.tx.AdminUtils.sudo_set_max_allowed_validators({
  netuid,
  max_allowed_validators,
});

Version History

v138 block 1,907,363 2 args
v290 block 5,947,548 2 args Current

Runtime Info

View Source
Pallet Index
19
Call Index
25
First Version
v138
Current Version
v411