Glossary
What each metric means, its exact formula, the API request behind it, and why it can differ from other explorers.
For AI agents: llms.txt
- APY / APR 7D (validator)
What delegating to this validator has returned over the last 7 days, annualised: APR without compounding, APY with.
Formularate per epoch = Σ dividends paid to delegators / Σ stake that earned them, over the last 7 complete UTC days. epochs per year = 7200 × 365 / the subnet tempo. APR = rate × epochs per year × 100; APY = ((1 + rate)^(epochs per year) − 1) × 100. Both ×100 and clamped to [0, 10000].The series is what the chain actually paid delegators, already net of the validator take and of childkey redistribution, measured against the exact stake the chain used as the denominator. The only difference between the two figures is the compounding assumption: APR is the number most explorers publish, often labelled APY, while APY is the more honest one for a passive alpha staker, since dividends restake into the pool. Annualisation uses each subnet's own tempo rather than a flat epoch count. Exactly 10000 means the real figure was clamped, not that it is precisely 10000%. A hotkey with no dividends in the window reads 0, and stale values are never carried forward. The list figure is the stake-weighted average of the validator's per-subnet rows.
API request
GET https://api.taoswap.org/validators/Response field
results[].apy_7d / results[].apr_7d- Delegator / Validator Earnings per Day
What the validator paid out over the last full day, in TAO: the first figure is what its delegators shared, the second what it kept as commission.
FormulaΣ TAO paid over the last complete UTC day, split at the take: the delegators' side is net of it, the validator's side is the take itself.A single day, not a rate, so it moves with the stake behind the hotkey and with what its subnets emitted that day: a large validator out-earns a small one at the same APY. The childkey-take slice is counted inside these figures, not on top of them. A validator running a 0% take reads 0 on its own line while still paying its delegators in full. Only the validator's own page carries them, so a list of validators compares yields instead.
API request
GET https://api.taoswap.org/validators/<hotkey>/Response field
delegator_daily_earning / validator_daily_earning- Delegators
How many delegators are staking to the validator.
API request
GET https://api.taoswap.org/validators/Response field
results[].count_delegators- Dominance
What proportion of all validator stake on the network this one validator controls.
Formulatotal_stake / Σ total_stake (chain-wide) × 100Same slippage-aware valuation as Total Stake. The list only sums validators with at least 1000 τ, so the visible set adds to ~100%. A validator's own page can read slightly lower than the list, because the two do not always count the same set. Validators under 1000 τ have no page of their own.
API request
GET https://api.taoswap.org/validators/Response field
results[].dominance- Fees (take)
The commission the validator keeps out of its delegators' rewards.
API request
GET https://api.taoswap.org/validators/Response field
results[].take- Nominators / Validator / Childkey 7D (τ)
The TAO a validator earned on one subnet over the last 7 days, split three ways: what went to its nominators, what it kept as commission, and the part that came from childkey take.
FormulaΣ TAO earned on that subnet over the last 7 complete UTC days. Nominators is net of the take, validator is the take itself, childkey is the childkey-take slice of the two.Amounts, not rates: they scale with the stake behind the hotkey, which is why the APY sitting beside them can be high on a small line and modest on a large one. Blank until the subnet has synced, which is not the same as zero. The childkey figure is a slice of the other two, so adding all three double-counts it.
API request
GET https://api.taoswap.org/validators/<hotkey>/Response field
monitoring[].nominator_return_7d_tao / validator_return_7d_tao / childkey_return_7d_tao- Root stake / Alpha stake (validator)
The two halves of a validator's total stake: TAO staked on root, and alpha staked across subnets (valued in TAO).
Formulatotal_stake_root + total_stake_alpha = total_stakeThe alpha half carries the same slippage-aware valuation as Total Stake, so it moves with pool depth as well as with price.
API request
GET https://api.taoswap.org/validators/Response field
results[].total_stake_root / results[].total_stake_alpha- Root weight (validator)
The validator's root stake counted the way the chain counts it for emission, where TAO on root does not weigh 1:1 against alpha.
Formulatotal_stake_root × γ, γ being the chain tao weight (~0.18, read live)A scaled TAO amount, not a ratio and not a second stake bucket, so never add it to the stake columns. Same γ as the subnet Root Proportion.
API request
GET https://api.taoswap.org/validators/Response field
results[].root_weight- Total Stake (validator)
Everything a validator has behind it, root stake plus alpha across every subnet, expressed in TAO.
FormulaΣ over subnets of each position valued in TAO (root 1:1; alpha through the pool, with slippage)Alpha is valued at what it would really fetch on exit, position by position, not at flat spot and not at the moving price. So it reads lower than a naive Σ(alpha × price) for large positions, and lower still than EMA-based explorers. The Accounts table values alpha exactly the same way, so the two are directly comparable. It is a snapshot from the last sync.
API request
GET https://api.taoswap.org/validators/Response field
results[].total_stake