RootClaimTypeSet
Event Re-added v334 → v362, v365 → v367, v372 → v377, v385 → current #113Emitted when a coldkey sets their root emission claim type.
View events on chainThe Big Picture
Root emissions can be handled different ways - automatically distributed, manually claimed, auto-staked, etc. RootClaimTypeSet configures your preference. It's like setting up direct deposit vs paper checks - same rewards, different delivery method. Your choice affects convenience and compounding behavior.
Why This Matters
Your root claim type determines whether rewards come automatically or you need to actively claim, and whether they go to liquid TAO or auto-stake. Setting the right type for your workflow saves time and potentially optimizes compounding.
Example Scenario
You want root emissions to auto-compound. You set your claim type to auto-stake. RootClaimTypeSet fires confirming your preference. Future root emissions automatically stake to your designated hotkey instead of sitting as liquid TAO requiring manual action.
Common Questions
- What claim types are available?
- Typically options include: manual claim, auto-distribute to balance, auto-stake, etc. Check the RootClaimType enum in the runtime for current options.
- Can I change my claim type anytime?
- Yes, set a new type to update your preference. Changes apply to future emissions, not already-accumulated ones.
- What's the default claim type?
- There's usually a default (often manual claim). If you haven't set a type, you're using the default. Check your current setting if unsure.
Use Cases
- Configure how your root rewards are distributed
- Set up automatic vs manual claiming preferences
- Track claim type configurations across the network
- Build root emission management tools
How to Use This Event
- → Monitor your claim type configuration changes
- → Track network-wide claim type preferences
- → Build preference management interfaces
From Chain Metadata
Root claim type for a coldkey has been set. Parameters: (coldkey, u8)
Triggers
Emitted by
Preconditions
- Coldkey is valid account
Effects
Storage Modified
Postconditions
- Claim type stored for future distributions
Side Effects
- Affects how root emissions are handled
Event Data
| # | Name | Type | Description |
|---|---|---|---|
| 0 | coldkey | AccountId | Cold wallet address (offline storage) (hex -> SS58) |
| 1 | root_claim_type | RootClaimTypeEnum | root_claim_type (RootClaimTypeEnum) |
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 RootClaimTypeSet events
api.query.system.events((events) => {
events
.filter(({ event }) =>
event.section === stringCamelCase("SubtensorModule") &&
event.method === "RootClaimTypeSet"
)
.forEach(({ event }) => {
console.log("RootClaimTypeSet:", event.data.toHuman());
});
});Version History
Runtime Info
View Source- Pallet Index
- 7
- Event Index
- 113
- First Version
- v334
- Current Version
- v393