SubnetOwnerHotkey

Storage Map v233 → v411

Hotkey associated with subnet owner .

Explore chain
Queried by: subnet ownersdevelopersanalytics

The Big Picture

Subnet owners have an associated hotkey for receiving emissions and performing owner operations. This maps each subnet to its owner hotkey.

Use Cases

  • Find owner hotkey for a subnet
  • Verify owner operations
  • Build owner management tools

From Chain Metadata

MAP ( netuid ) --> subnet_owner_hotkey

Purpose & Usage

Purpose

Link subnet ownership to a specific hotkey.

Common Query Patterns

  • Query by netuid

Query Keys

#NameTypeDescription
1
netuid
u16 netuid (u16, hashed key component)

Stored Value

subnet_owner_hotkey (AccountId)

Decoding the value

AccountId (32-byte hex)

Bittensor uses SS58 prefix 42 for both hotkeys and coldkeys. The 32 bytes are sr25519 public keys.

value as `0x${string}` // 32-byte AccountId

Relationships

Modified By

Related Events

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);

// Query SubnetOwnerHotkey storage
const netuid = 1;

const result = await api.query.SubtensorModule.SubnetOwnerHotkey.getValue(netuid);
console.log("SubnetOwnerHotkey:", result);

Version History

v233 block 4,920,350 Added
v278–v289 · runtime versions skipped on chain (never deployed)
v290 block 5,947,548 Internal re-bind Current

Runtime Info

View Source
Pallet
SubtensorModule
Storage Kind
Map
First Version
v233
Current Version
v411