set_root_claim_type
Call v334 → current #122Sets how root emissions are claimed/distributed.
View calls on chainCall Workflow
Click items to navigate. Pan and zoom to explore.
The Big Picture
Root emissions can be handled different ways: accumulate pending (manual claim), auto-stake to a hotkey, or other distribution methods. set_root_claim_type configures which approach you want. This is a set-and-forget configuration that affects all future emissions.
Why This Matters
How you receive emissions affects compounding, taxes, and workflow. Auto-stake means hands-off compounding but less control. Manual claim means more transactions but precise control over when rewards convert to liquid or stake.
Example Scenario
You want root emissions to auto-compound to your main validator. Call set_root_claim_type(claim_type='auto_stake', destination=main_hotkey). Now root earnings automatically stake to your validator instead of accumulating as pending claims.
Common Questions
- What are the claim type options?
- Typically: manual (accumulate pending), auto-stake (to specified hotkey), or possibly direct-to-balance. Check current network implementation for exact options.
- Can I change claim type at any time?
- Yes - it only affects future emissions. Already pending emissions use the old behavior. Claimed emissions are unaffected.
- Does claim type affect taxes?
- Possibly - consult a tax professional. Some jurisdictions treat auto-staked rewards differently than manually claimed. Your configuration might have tax implications.
Use Cases
- Configure auto-stake vs manual claim preference
- Set up automatic compounding of root emissions
- Choose emission destination (liquid vs staked)
- Optimize tax or accounting treatment of rewards
From Chain Metadata
Sets the root claim type for the coldkey.
Input Parameters
| # | Name | Type | Description |
|---|---|---|---|
| 0 | new_root_claim_type | RootClaimTypeEnum | new_root_claim_type (RootClaimTypeEnum) |
Permissions
Permission data inferred from metadata. May be incomplete.
Requirements
- Coldkey is valid
- Valid claim type specified
Effects
Events Emitted
Storage Modified
Postconditions
- Claim type stored
- Future emissions follow new claim behavior
Side Effects
- Affects future emission handling
- May change auto-stake behavior
Code Examples
// ----------------------------------------------------------------------
// HEADS UP: 1 arg below has a complex type with no usable default.
// Look for `undefined as any` and replace it with real value
// before running — the snippet compiles, but will fail at runtime as-is.
// ----------------------------------------------------------------------
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);
// Build set_root_claim_type call (typed, named args)
const new_root_claim_type = undefined as any /* RootClaimTypeEnum — replace with real value */;
const tx = api.tx.SubtensorModule.set_root_claim_type({
new_root_claim_type,
});Runtime Info
View Source- Pallet Index
- 7
- Call Index
- 122
- First Version
- v334
- Current Version
- v411