IdentitySet

Event v136 → current #0

Emitted when a user registers or updates their on-chain identity .

Useful for: validatorssubnet ownersanalyticswalletsdevelopers

The Big Picture

Identity registration is how accounts become 'known' in the ecosystem. Validators use identity to make themselves discoverable to delegators. Subnet owners use it to provide contact information. This event signals that an account has opted into public visibility with verifiable metadata.

Why This Matters

When someone registers their identity, they're making a commitment to public visibility. This is a trust signal - they're willing to be known and contacted. For delegators, this event helps discover new validators entering the ecosystem.

Example Scenario

A new validator registers their identity with 'Bittensor Labs' display name and website. IdentitySet fires with their account. Your delegation dashboard can now show this validator with their display name instead of just a hex address.

Common Questions

Does this event fire for updates too?: Yes, IdentitySet fires for both new registrations and updates to existing identities. Check if the account had a previous identity to distinguish new vs update.
What information is included in the event?: The event includes the account that registered. To get the actual identity info, query Registry.IdentityOf(account) after receiving the event.

Use Cases

Track when validators register their identities
Build validator discovery and reputation systems
Monitor identity registrations for ecosystem growth metrics
Trigger notifications when accounts add identity info

How to Use This Event

→ Subscribe to build a directory of registered identities
→ Index all events to track identity registration trends
→ Monitor specific accounts for identity changes
→ Build reputation scoring based on identity longevity

Part of: Identity Registry

Triggers

Emitted by

set_identity

Preconditions

Account has sufficient balance for identity deposit
Number of additional fields is within MaxAdditionalFields limit
Identity info is well-formed

Effects

Storage Modified

IdentityOf

Postconditions

Identity metadata stored in IdentityOf
Deposit reserved from account balance
Account is now discoverable with registered metadata

Side Effects

Previous identity (if any) is overwritten
Deposit amount may change if field count differs from previous

Event Data

#	Name	Type	Description
0	who	AccountId	Account that registered or updated their identity (hex -> SS58)

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

// Subscribe to IdentitySet events
api.query.system.events((events) => {
  events
    .filter(({ event }) =>
      event.section === stringCamelCase("Registry") &&
      event.method === "IdentitySet"
    )
    .forEach(({ event }) => {
      console.log("IdentitySet:", event.data.toHuman());
    });
});

Runtime Info

View Source

Pallet Index: 17
Event Index: 0
First Version: v136
Current Version: v393

Back to Registry Events