ChainIdentitySet

Event v195 → v212, v216 → v247, v252 → v265, v273 → v277, v290 → v315, v320 → v326, v334 → v367, v372 → v377, v385 → v402, v411 → current Changed in v411 #76

Emitted when on-chain identity is set for a hotkey .

View events on chain

Useful for: validatorsminersdelegatorsanalyticswallets

The Big Picture

Hotkeys can have on-chain identity - name, description, website, etc. This helps delegators identify who they're staking with. A validator named 'TrustableValidator' with website and contact info is more credible than anonymous hotkey '5Grw...QY'. Identity is optional but valuable for building reputation.

Why This Matters

As a validator, identity helps you stand out and build trust. As a delegator, checking validator identities helps you make informed choices. This event signals when a hotkey establishes or updates their public identity.

Example Scenario

You're launching a validator and want delegations. You set your identity: name 'ReliableNode', website 'reliablenode.io', contact '[email protected]'. ChainIdentitySet fires. Now explorers and delegation tools show your branding instead of just a hex address. Delegators can verify who you are.

Common Questions

Is identity required to be a validator?: No, but strongly recommended. Anonymous validators get fewer delegations because trust is harder to establish. Identity is about reputation building.
Can I verify a validator's identity claims?: The chain stores what they claim, but doesn't verify. Check their website, contact them, verify consistency. Community reputation matters.
What info should I include in my identity?: At minimum: name and contact method. Ideally: website, social links, and anything that helps delegators verify you're legitimate and reachable.

Use Cases

Brand your validator with name and contact info
Help delegators identify trustworthy validators
Track validator identity changes
Build validator discovery and reputation tools

How to Use This Event

→ Monitor your validators for identity updates
→ Build validator directories with identity info
→ Track identity adoption across validators

From Chain Metadata

The identity of a coldkey has been set

Triggers

Emitted by

set_identity

Preconditions

Caller owns the hotkey
Valid identity data provided

Effects

Storage Modified

IdentitiesV2 LastTxBlock

Postconditions

ChainIdentity or ChainIdentityOf updated

Side Effects

Hotkey displays identity info on chain

Event Data

#	Name	Type	Description
0	arg0 → account	AccountId	Account address (32 bytes, SS58-encoded) (hex -> SS58)

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

// Subscribe to ChainIdentitySet events
client.finalizedBlock$.subscribe(async (block) => {
  const events = await api.event.SubtensorModule.ChainIdentitySet.get(block.hash);
  for (const evt of events) {
    console.log("ChainIdentitySet:", evt.payload);
  }
});

Version History

Version:

v195 block 3,791,350 1 args

v216 block 4,510,996 1 args

v252 block 5,163,656 1 args

v273 block 5,659,032 1 args

v290 block 5,947,548 1 args

v320 block 6,523,566 1 args

v334 block 6,811,690 1 args

v372 block 7,430,358 1 args

v385 block 7,782,670 1 args

v411 block 8,283,784 1 args Current

Runtime Info

View Source

Pallet Index: 7
Event Index: 76
First Version: v195
Current Version: v411

Back to SubtensorModule Events