RootClaimed

Event v334 → v362, v365 → v367, v372 → v377, v385 → v402, v411 → current Changed in v411 #113

Emitted when a coldkey claims their root network emissions .

Useful for: validatorsstakersanalyticsdeveloperswallets

The Big Picture

The root network (subnet 0) is special - it allocates emissions across all other subnets. Participants in the root network earn emissions for their role in this meta-level coordination. RootClaimed fires when you collect these accumulated root emissions. It's separate from subnet-specific emissions - this is your reward for participating in network-level governance and coordination.

Why This Matters

If you participate in the root network (setting weights on subnets, contributing to meta-consensus), you earn root emissions. These accumulate until claimed. RootClaimed confirms you received your pending root rewards - it's payday for your root network contribution.

Example Scenario

You're a root network validator, setting weights on which subnets deserve emissions. Over time, root emissions accumulate in your account. You call claim_root_rewards, and RootClaimed fires showing 5 TAO distributed to your coldkey. If you have auto-stake configured, this might immediately restake.

Common Questions

How do I earn root emissions?: Participate in the root network (subnet 0). This typically means being a validator with sufficient stake who sets weights on subnet allocations.
Are root emissions automatic or do I need to claim?: It depends on your RootClaimType setting. Some types auto-distribute, others require manual claims. Check your claim type configuration.
How are root emissions different from subnet emissions?: Subnet emissions reward you for work on a specific subnet (mining/validating). Root emissions reward you for meta-level participation in how emissions are allocated across all subnets.

Use Cases

Claim accumulated root network rewards
Track root emission distributions
Monitor validator root rewards
Build root emission tracking dashboards

How to Use This Event

→ Track your root emission claims over time
→ Monitor root network participation rewards
→ Build aggregate income tracking including root rewards

From Chain Metadata

Root emissions have been claimed for a coldkey on all subnets and hotkeys. Parameters: (coldkey)

Triggers

Emitted by

claim_root

Preconditions

Coldkey has unclaimed root emissions
Claim operation executed

Effects

Storage Modified

PendingRootAlphaDivs RootClaimed

Postconditions

Root emissions distributed to coldkey
Pending emissions cleared

Side Effects

May trigger staking if auto-stake enabled

Event Data

#	Name	Type	Description
0	coldkey	AccountId	coldkey: 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 RootClaimed events
client.finalizedBlock$.subscribe(async (block) => {
  const events = await api.event.SubtensorModule.RootClaimed.get(block.hash);
  for (const evt of events) {
    console.log("RootClaimed:", evt.payload);
  }
});

On-Chain Activity

Emission Frequency

●●●●○○ Significant 1M–5M emissions

Major features with millions of emissions

#17 most emitted event

As of block 7,429,232

Version History

Version:

v334 block 6,811,690 1 args

v365 block 7,135,419 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: 113
First Version: v334
Current Version: v411

Back to SubtensorModule Events