# Taostats Docs — Start here

> Taostats is the block explorer, data API and analytics platform for Bittensor and the TAO token. These docs cover the Taostats API, the MCP server, the TypeScript SDK, Bittensor Auth, the apps, and the Bittensor concepts behind them.

The "Start here" section of https://beta.taostats.io/docs. The index of every docs page is https://beta.taostats.io/llms.txt and the whole corpus is https://beta.taostats.io/llms-full.txt. Each page below is also available on its own at the `_Source:` URL with `.md` appended.

---

# Getting started with the Taostats API

Sign up at Taostats Pro with Google, GitHub or email, then create your first API key.

_Source: https://beta.taostats.io/docs/start-here/getting-started-with-taostats-api_

_Last reviewed: 2026-09-14_

## Get an API key

Visit [https://taostats.io/pro/](https://taostats.io/pro/) to sign up for an API key.

1. Sign in with your favorite 3rd party authentication.

   ![Taostats API sign-in screen headed "Get Started with the taostats API today" with three buttons: Sign in with Google, Sign in with Github, and Sign in with Email](https://beta.taostats.io/images/docs/start-here/taostats-api-signin-page.jpg)
2. ![Taostats API dashboard for a project showing a "Create API Key" button and a Usage section](https://beta.taostats.io/images/docs/start-here/taostats-api-create-api-key-project.jpg)
3. Click Create API key to generate your API key.

---

# Model Context Protocol (MCP)

Give an LLM live access to Bittensor chain and account data through the Taostats MCP server.

_Source: https://beta.taostats.io/docs/start-here/model-context-protocol-mcp_

_Last reviewed: 2026-09-14_

Use taostats in your Vibe coding/ bot creation.

## Implementation details

[https://mcp.taostats.io/](https://mcp.taostats.io/)

## What is MCP?

Large Language Models (LLMs) are trained on data.  But, it does not know everything - what if the pages are not indexed?  What if the data is private?

A Model Context Protocol (MCP) fixes that.  It tells your LLM - "here is some specialized information that will help you answer questions."  MCPS are often used by developers"

* Database access: if claude code or Copilot actually know the tables, and the data in the tables - it won't spit out code with "fill in the details" - it will fill in the details
* Proproietary information:  Chatbots for insurance companies can look up your account - and claim status.  The shipping bot can track your order.  These wouldn't be in e normal LLM context, but the MCP gives access to that data.

## Taostats MCP

Your LLM will not know the balance of wallet 5Hd2ze5ug8n1bo3UCAcQsf66VNjKqGos8u6apNfzcU86pg4N.  It changes minute by minute.

But if you add in the taostats MCP - the LLM can look for the taostats account endpoint - call the endpoint, and tell you that the balance is 508,379.9377 (accurate as of 2/16/2026 0947 EST).

* Alerting bots - sorted
* Trading bots - data is sorted (be careful!)
* Bittensor app building - sorted.

Al you need is an API key and to follow the setup instructions!

---

# Taostats governance

Raise proposals and vote with weight drawn from your on-chain holdings, off-chain and with no gas or fees.

_Source: https://beta.taostats.io/docs/start-here/taostats-governance_

_Last reviewed: 2026-09-14_

Taostats Governance lets the Bittensor community raise proposals and vote with weight drawn from real on-chain holdings — with no gas, no fees, and nothing written on-chain. It is available at [governance.taostats.io](https://governance.taostats.io/how-it-works).

> [!NOTE]
> **Completely free, completely off-chain.** Voting and raising proposals cost nothing. You sign a one-time message to prove you own your coldkey, but never an on-chain transaction — no gas, no funds move. Governance here is an off-chain signal, weighted by your verified on-chain balances.

## How it works

1. **Sign in.** Sign in with Taostats and sign a one-time message to prove you own your coldkey. This is off-chain — no transaction, no gas, nothing moves.
2. **Pick an option.** Open a proposal, choose your option, and cast your vote. One vote per coldkey.
3. **Weighted by holdings.** Your weight is read from your on-chain balances. Subnet polls use your 30-day average alpha in that subnet; root polls use your 30-day average TAO-equivalent across all holdings.
4. **Frozen & fair.** Your weight is locked in at your first vote. You can change your option (once per epoch), but the weight stays fixed. Averaging over 30 days stops last-minute stake-loading from buying votes.

## The details

- **One vote per coldkey.** Multiple hotkeys under one coldkey still count as a single vote, weighted by the coldkey's aggregate holdings.
- **Who can propose.** Anyone holding at least 1 TAO-equivalent in a poll's scope can raise a proposal in it.
- **Conviction weighting (optional).** A proposal can count locked (convicted) alpha more heavily, or restrict eligibility to convicted alpha only. Every poll shows its exact rule under *"How this poll is weighted."*
- **Transparent.** Every vote, its weight, and the full audit log are public. Shared links never include your coldkey or hotkey.

## Poll scopes

| Scope | Voting weight |
| --- | --- |
| **Subnet poll** | Your 30-day average alpha in that subnet |
| **Root poll** | Your 30-day average TAO-equivalent across all holdings |

> [!NOTE]
> **Why the 30-day average?** Reading a rolling 30-day balance rather than a live snapshot prevents anyone from loading stake immediately before a vote to inflate their weight, then unwinding it afterwards. Governance weight reflects sustained holdings, not a momentary position.

## Get started

Head to [governance.taostats.io](https://governance.taostats.io/how-it-works), sign in with Taostats, and cast your first vote — no wallet transaction required.

---

# Bittensor Auth

Standard OAuth2 and OIDC authentication backed by Bittensor on-chain identity and permissions.

_Source: https://beta.taostats.io/docs/start-here/bittensor-auth_

_Last reviewed: 2026-09-14_

Bittensor Auth is standard OAuth authentication powered by on-chain identity and permissions. It lets any application use Bittensor wallets as identities and on-chain state as access control, through the Taostats Auth Gateway. Learn more at [taostats.io/bittensor-auth](https://taostats.io/bittensor-auth) or test flows at [auth.taostats.io](https://auth.taostats.io).

> [!NOTE]
> **Works with any OAuth2 or OIDC library** — no custom SDK required. Because it is standard OAuth2/OIDC, it drops into off-the-shelf tools such as Grafana, JupyterHub, Gitea, Nextcloud, FastAPI, and NextAuth.js.

## The problem

Bittensor identity has no standard authentication layer, so today:

- Custom auth gets rebuilt for every subnet.
- OAuth doesn't understand miners or stake.
- Off-the-shelf tools can't authenticate against the chain.
- You can't log in with a browser wallet.

## The solution: OAuth backed by the chain

The Taostats Auth Gateway connects Bittensor identity to the existing OAuth ecosystem:

- **Wallet = Identity**
- **Chain state = Permissions**
- **OAuth = Access token**

## How it works

1. App requests login.
2. Redirect to Taostats Auth.
3. Wallet signs the authentication challenge.
4. On-chain verification.
5. JWT token issued.
6. Application grants access.

> [!NOTE]
> **Permissions follow the chain automatically.** On-chain scopes are re-verified at every token refresh. If a miner deregisters, their access lapses automatically at the next epoch — no manual revocation.

## On-chain scopes

Scopes verify a condition against on-chain state at authentication and on every refresh:

| Scope | Verifies |
| --- | --- |
| `subnet:1:miner` | Registered miner |
| `subnet:1:validator` | Validator |
| `subnet:18:owner` | Subnet owner |
| `subnet:1:holder:100` | Alpha holder (threshold) |
| `tao:holder:50` | TAO holder (threshold) |
| `delegate:{hotkey}` | Delegator relationship |
| `staker:1000` | Network stake (threshold) |

## Auth flows

| Flow | Use |
| --- | --- |
| **Authorization Code + PKCE** | Standard web application login |
| **Device Code Flow** (RFC 8628) | CLI and headless authentication |
| **OpenID Connect** | Full OIDC compatibility |

## Use cases

- **Headless miner auth** — CLI authentication using Device Code Flow (RFC 8628).
- **Validator dashboards** — gate access to subnet validators; access auto-revokes when deregistered.
- **Token-gated content** — serve different content at different holder thresholds.
- **Subnet owner portals** — verify subnet ownership automatically, no allowlist required.

## Developer integration

1. Standard OAuth2/OIDC — no custom SDK.
2. JWKS endpoint for resource-server validation.
3. Token claims include `hotkey`, `coldkey`, `scope`, and `sub`.

## Trust & security

Bittensor Auth is a centralised layer on a decentralised system — and it is open source and self-hostable.

- **Hosted service** — configure an auth client with Taostats Pro.
- **Self-hosted** — run your own gateway.
- **Explore** — test flows at [auth.taostats.io](https://auth.taostats.io).

## Get started

[Configure an auth client](https://taostats.io/bittensor-auth) with Taostats Pro, or [view the project on GitHub](https://github.com/taostat/auth-gateway) to self-host your own gateway.

---

# Taostats iOS and Android

Track your wallets and stake on the go with the Taostats mobile app for iOS and Android.

_Source: https://beta.taostats.io/docs/start-here/mobile-apps-ios-and-android_

_Last reviewed: 2026-09-14_

The Taostats Mobile app - lets you track and stake on the go

- [Download on the App Store](https://apps.apple.com/gb/app/taostats/id6751163947)
- [Get it on Google Play](https://play.google.com/store/apps/details?id=io.taostats.mobile)

Download the taostats mobile app to track your wallets on the go.

More at [https://taostats.io/app](https://taostats.io/app)

---

# Taostats Chrome Extension

Hold, watch and stake from your Bittensor wallets in the browser with the Taostats Chrome extension.

_Source: https://beta.taostats.io/docs/start-here/taostats-chrome-extension_

_Last reviewed: 2026-09-14_

A chrome extension giving access to your wallets on chain

![Taostats Chrome extension wallet popup showing total portfolio with hidden balances, Send and Receive buttons, and a list of saved accounts](https://beta.taostats.io/images/docs/start-here/taostats-chrome-extension-wallet-popup.png)

## Installation

from the [Chrome Extensions Store](https://chromewebstore.google.com/detail/taostats-the-bittensor-wa/khdnjjgidjjbjpececegbfglalchffpo).  You can get marketing information about the app at [https://taostats.io/wallet-extension](https://taostats.io/wallet-extension)

## Add your wallet

You need to add your wallet address to the extension:

![Taostats Chrome extension account toolbar with the "+" add-account button hovered, showing its "Add account" tooltip](https://beta.taostats.io/images/docs/start-here/taostats-chrome-extension-add-account-button.png)

You have 4 options:

![Taostats Chrome extension add-wallet menu with four options: New Bittensor Account, Import via Recovery Phrase, Watch Bittensor Account, and Connect Ledger](https://beta.taostats.io/images/docs/start-here/taostats-chrome-extension-add-wallet-options.png)

1. New account:  Will create a new 5xxx account on chain for you.
2. Import using your seed phrase (mnemonic)
3. Watch an account - get details, track balances, but you cannot trade.
4. Ledger - connect your ledger to Taostats.

## stake

![Taostats Chrome extension wallet view with hidden balances and inline Stake and Unstake buttons on the TAO row above subnet positions](https://beta.taostats.io/images/docs/start-here/taostats-chrome-extension-stake-unstake.png)

For any wallet/any position, you can stake/unstake right from the wallet. (note that balances are hidden. This is also a feature of the extension.  When not taking screenshots for the docs - you can see your actual balances.)

---

# TypeScript SDK

Install @taostats/sdk for typed access to the Taostats API and direct RPC access to the Bittensor chain.

_Source: https://beta.taostats.io/docs/start-here/typescript-sdk_

_Last reviewed: 2026-09-14_

Are you a TypeScript developer using our APIs?  Our SDK might slimplify things!

Our Typescript SDK is now available. It offers full access to the Taostats API, but also full customized RPC access to the Bittensor chain.

IN addition to making calls to Taostats, you can do any transaction on the chain using the RPC nodes.

## Installation

The Taostats [TypeScript SDK](https://github.com/taostat/ts-sdk) is available on GitHub.  The latest installation instructions can be found there.

Requirements: Node.js v 22.3.0 or higher

```shell
npm install @taostats/sdk
# or
yarn add @taostats/sdk
# or
pnpm add @taostats/sdk
```

### Setup

the `.env` has three variables:

```
TAOSTATS_API_KEY='your-taostats-api-key'

# Only needed to interact with certain blockchain modules(stake, unstake, transfer, move) 
TAO_ACCOUNT_SEED="your twelve word seed phrase"
# OR
TAO_ACCOUNT_PRIVATE_KEY="your_private_key_in_hex"

RPC_URL="wss://your_custom_url" #Optional
```

* **TAOSTATS\_API\_KEY**: Your API key. Required to make API calls with Taostats
* **TAO\_ACCOUNT\_SEED**: Your 12 word wallet phrase.  Used for RPC calls on chain.  BE CAREFUL!  The .gitignore is properly set, but if your server is compromised, you may loose access to your wallet.
* **TAO\_ACCOUNT\_PRIVATE\_KEY**: A hex encoded version of your private key.  Used for RPC calls on chain.  BE CAREFUL!  The .gitignore is properly set, but if your server is compromised, you may loose access to your wallet.
* **RPC\_URL**: Change to run your code in testnet, or in a private node.

## Usage

### API Modules

The modules below mirror the Taostats API surface. New endpoints are added over time — for the complete, current set see the [API Reference](https://beta.taostats.io/docs/api-reference) or the SDK's own type definitions.

Parameters are all identical to those in the API

* client.taoPrices - TAO price and market data endpoints
  * getTaoPrice
  * getTaoPriceHistory
  * getTaoPriceOHLC
* client.tradingView - TradingView UDF history data for subnets
  * getTradingViewHistory
* client.delegations - Delegation/staking data, slippage calculations, and stake balances
  * getSlippage
  * getDelegationEvents
  * getStakeBalanceSumInTao
  * getdTaoStakeBalance
  * getdTaoHistoricalStakeBalance
* client.accounts - Account information, balances, and transactions
  * getAccount
  * getAccountHistory
  * getTransfers
  * getOnChainIdentity
* client.chain - Blockchain data including blocks, extrinsics, events, and network statistics
  * getBlocks
  * getBlockNumbersByInterval
  * getExtrinsics
  * getEvents
  * getChainCalls
  * getLatestStats
  * getStatsHistory
  * getRuntimeVersion
  * getRuntimeVersionHistory
  * getProxyCalls
* client.subnets - Subnet data, registration, pricing, and comprehensive analytics
  * getSubnets
  * getHistoricalSubnetPricesSum
  * getLatestSubnetPricesSum
  * getSubnetRegistrations
  * getSubnetRegistrationCostHistory
  * getCurrentSubnetRegistrationCost
  * getSubnetOwner
  * getSubnetIdentity
  * getSubnetEmission
  * getSubnetsPoolsHistory
  * getCurrentSubnetPools
  * getSubnetHistory
* client.metagraph - Metagraph data including miner incentive distributions
  * getMinerIncentiveDistributionBySubnet
  * getSubnetAxonIpDistribution
  * getSubnetColdkeyDistribution
  * getLatestMinerWeight
  * getMinerWeightHistory
  * getNeuronDeregistrations
  * getNeuronRegistrations
  * getRootSubnetHistory
  * getRootSubnet
  * getHistory
  * getLatest
* client.live - Real-time blockchain data and live network information
  * getFreeTaoBalance
  * getLatestBlockExtrinsics
  * getExtrinsicsForBlockRange
  * getExtrinsicsForSpecificBlock
  * getRawExtrinsicsForSpecificBlock
  * getNodeTransactionPool
  * getNodeVersion
  * getPalletByConstants
  * getPalletEvents
* client.evm - EVM-related operations and data
  * getEVMTransactions
  * getEVMBlocks
  * getEVMContracts
  * getEVMLogs

---

# FAQ

Answers to the questions we are asked most about the metagraph, dTao, staking, mining, TAO and security.

_Source: https://beta.taostats.io/docs/start-here/faq_

_Last reviewed: 2026-09-14_

## General

### What is the Metagraph?

The metagraph is a tabular output of the data metrics associated to all subnets participants at any given moment in time.  It can be accessed via the `btcli s metagraph`, but for easy sorting and organisation of the data, [taostats](https://taostats.io) displays this data for the community with some additionally calculated fields that are not in the CLI version.

## dTao

### What is dTao?

In February 2025, a new emissions paradigm known as dTao was launched. Its goals: further decentralise Bittensor by making emissions to subnets a purely democratic process. Staking tao into a subnet (as alpha) increases the emissions to that subnet.  Emissions are determined by "voting with their stake." Since spec 440, this demand no longer maps straight to a subnet's share: an [emission gate](https://beta.taostats.io/docs/concepts/protocol-changes/emission-gate) redistributes emission from the low-demand tail to the winners above the bar.

Emissions are fundamentally changed as a part of dTao. See: [Subnet emission overview](https://beta.taostats.io/docs/concepts/how-emission-works/split-alpha-out)

### The first block of dTao was 4920351

### What happened tp my stake at launch?

Your stake was converted to `root stake` and continues to earn rewards.  See  [Stakeholder Emissions: Root](https://beta.taostats.io/docs/concepts/how-emission-works/stakeholder-emissions-root).

## Staking/Delegation

### I don't see my staking rewards!

Go to `taostats.io/account/<coldkey>`.  Mouse over the chart, and you'll see the staking number increase over time.  Staking reward are added to your wallet once every epoch - \~72 minutes.

### I have some tao. Which validator should I delegate it to?

Awesome - welcome to Bittensor.  The [Taostats: For Staking](https://beta.taostats.io/docs/concepts/staking/taostats-for-staking) page has detailed information to help you decide which validator to stake with. There is no hold period for staking/unstaking.  If you are looking for a suggestion, we like taostats and Corcel.

### Is staking/delegation safe? Will the validator take my stake?

Under dTao, when you stake, tao is converted to the destination subnet's alpha at stake time and that alpha is committed to the validator's hotkey. Your stake remains under your coldkey — the validator has no access to it, and you may unstake at any time (rate limits do apply - the current hotkey stake/unstake rate limit is 1x per 360 blocks). Rewards are paid in that subnet's alpha and credited to the hotkey you staked to.

### Is the [Taostats delegation](https://delegate.taostats.io/)  tool safe? Will Taostats have my wallet credentials?

It is safe. All staking is done on chain, and taostats does not get your seed phrase or wallet credentials.

### Why does Staking APY decrease over time?

The short answer is that the math guarantees it. See [Emissions: Root vs. Alpha Stake](https://beta.taostats.io/docs/concepts/how-emission-works/stakeholder-emissions-root-vs-alpha)  for the details.

### I staked into a subnet and my TAO has gone down. Why?

Staking into **subnet 0 (root)** is safe — there is no chance for your tao's value to decrease. Staking into **other subnets** is riskier: you are buying that subnet's alpha token, whose price can move against you.

First, check there are no transfers *out* of your wallet at `https://taostats.io/account/<your 5... address>`. If there are none, the change is almost certainly alpha price movement:

* If a subnet's alpha price is 0.1 and you spend 10 tao, you receive 100 alpha.
* If the price rises to 0.2, your 100 alpha is now worth 20 tao.
* If the price drops to 0.05, your 100 alpha is worth only 5 tao.

The alpha quantity you hold doesn't shrink — its value in tao rises and falls with the subnet price. See [Price Impact and Slippage](https://beta.taostats.io/docs/concepts/staking/slippage) and [Staking in dTao](https://beta.taostats.io/docs/concepts/staking/staking-in-dtao).

## Mining

### How do I get started?

[Starting as a Miner](https://beta.taostats.io/docs/concepts/miners/i-want-to-mine-on-bittensor): Grew into its own page.

### Why did I get de-registered?

Mining in Bittensor is competitive - there are a limited number of slots available to mine on each subnet.  If your miner falls to the bottom of the emission column in the metagraph of your subnet, it will be de-registered when a new neuron is registered. [Taostats: For Miners](https://beta.taostats.io/docs/understanding-taostats/miners/taostats-for-miners) shows how to read the metagraph to gauge the rank of your miner.

### My miner has zero emissions? is this a bug?

It is important to do you own research before registering on a subnet to understand how emission is granted to miners. Mining is extremely competitive, and using the base miner is often "not enough" to receive emissions.  Additionally, each subnet awards emission differently. Some Subnets only award emission to the top "x" miners. In others, the time to receive emission varies - but in general you'll need at least one epoch for the validators to grade you and set weights.

If the Subnet has no emissions:

![Discord message explaining that when a subnet has 0% emissions, the zero reward is still divided proportionally by weights, so some miners receive more of nothing than others](https://beta.taostats.io/images/docs/start-here/subnet-zero-emissions-discord-explanation.png)

## Tao

### How do I buy tao?

The [Tao Community exchange channel](https://discord.com/channels/1086368192521318472/1180148763067699241) has an updated list of exchanges.  The [wallet channel](https://discord.com/channels/1086368192521318472/1177226246048972820) contains information on wallets that support tao.

### How is tao distributed?

[Yuma Consensus](https://beta.taostats.io/docs/concepts/chain-runtime/consensus) is the consensus model used to distribute tao emissions. See the [How emission works](https://beta.taostats.io/docs/concepts/how-emission-works) flow for a step-by-step description of the emission and distribution mechanism.

## Security

### Is the data I send to a Bittensor secure? Can I send private information to a subnet?

Any data transmitted to Bittensor will pass through multiple servers, including a validator and a miner. There is no guarantee of data security, and you should use extreme caution in transmitting private or confidential information through the Bittensor network.

### There was a hack in July 2024. What happened?

From July 2-12, 2024, the chain was placed into safe mode - preventing transactions from being performed.  In the minutes before the chain was placed in safe mode, several large accounts were drained of tao.

The origins of the attack stem from the release of Bittensor 6.12.2 in May 2024. The pip version of this release had a compromised library that allowed the hacker to collect unencrypted coldkeys. On July 2, 2024, the attacker used these credentials to empty several wallets.  *ONLY* users of the command like tool BTCLI - version 6.12.2 - were compromised. [Blog post](https://blog.bittensor.com/bittnesor-community-update-july-3-2024-45661b1d542d)  describing the attack, and the [process to reopen the chain](https://blog.bittensor.com/reopening-bittensor-8252ee749980) . During the reopening and coldkey swap - no further wallets were attacked.
Our [A Best Practices Guide for Safely Installing Software](https://beta.taostats.io/docs/concepts/legacy-deprecated/a-best-practices-guide-for-safely-installing-software) provides a template for ensuring you are operating as safely as possible when installing dependencies.

## Hotkey/Coldkey What's the difference?

In Bittensor, your coldkey is your wallet. One coldkey can have many hotkeys.  Your coldkey is used to transfer and hold tao.  Hotkeys are used on the chain to register neurons (miners & validators), and stake tao on validators.  Tao that is earned on the hotkey is staked to the hotkey.  Upon de-registration or de-staking, the tao is transferred to the wallet's coldkey. [Coldkey/Wallets](https://beta.taostats.io/docs/api-reference/account) section has more information.

## Accounts

### Why was there a big drop in accounts in May 2024?

![Taostats area chart of total accounts over time: Total Accounts (orange) peak at 143,043 on 20 May 2024 then drop sharply by ~60,000, while Non-zero Accounts (teal, 78,512) keep rising](https://beta.taostats.io/images/docs/start-here/total-accounts-drop-may-2024-chart.png)

Due to a chain upgrade, all accounts had to be migrated, but this migration had impacts to the chain.  To mitigate this impact, empty accounts were not migrated. [twitter thread](https://x.com/taostats/status/1794719922486223324)

---

# Glossary

Definitions of the terms used across Bittensor and Taostats, from alpha through to weight copying.

_Source: https://beta.taostats.io/docs/start-here/glossary_

_Last reviewed: 2026-09-14_

List of commonly used terms in Bittensor and on Taostats.

## Alpha:

Each subnet has a token corresponding to its symbol (alpha, beta, delta....). To generalise subnet tokens, they are referred to as alpha.

Note [Liquid Alpha](#liquid-alpha) is a different term.

## Alpha in (aka Alpha pool, Alpha Reserve)

The amount of alpha that is present in the liquidity pool. Depending on the context, this can also refer to the amount of alpha being added to a pool during a block.

## Alpha out (aka Alpha outstanding, alpha staked)

The amount of alpha that has been staked onto hotkeys. Alpha\_out can refer to *all* of the alpha staked, or to the alpha being staked to a specific wallet. Examples: Subnet 37 has 4,000 alpha out. I have 100 alpha out staked from subnet 16.

Alpha\_out can also refer to the amount of alpha being added to the hotkeys during a block.

## Alpha Price:

This is defined by the ratio of tao\_in/alpha\_in ... the assets in the liquidity pool.

## Bittensor:

The peer-to-peer network for open machine intelligence. Bittensor is composed of independent subnets, each running its own incentive mechanism, connected through the [subtensor](#subtensor) chain. Nodes on subnets earn [tao](#tao) for producing work that other nodes rate as valuable. See [bittensor.com](https://bittensor.com/) for the whitepaper and network overview.

## Burn:

The permanent removal of tao from circulation. Burn is distinct from [recycle](#recycle): recycled tao re-enters the emission pool at a later date, whereas burned tao is destroyed. On Bittensor, "burn" in most registration and UI contexts actually means **recycle** — the tao is removed from circulation and re-emitted later, not destroyed. Transaction fees, for example, are recycled rather than permanently burned. See [Burning](https://beta.taostats.io/docs/concepts/tokenomics/burning).

## Child hotkey (Childkey):

A hotkey that receives delegated stake authority from a [parent hotkey](#parent-hotkey). The parent keeps custody of the coldkey and stake; the child registers on subnets and runs validator or miner workloads. Enables split of custody and operation. See [Emission for Parent/Child Hotkeys](https://beta.taostats.io/docs/concepts/how-emission-works/emission-parent-hotkeys).

## Coldkey:

The main key for a Bittensor wallet. It holds your funds and authorises transfers, purchases, sales, and staking/delegation. Because it can be kept offline (cold storage) and is only needed to sign fund-moving transactions, it is the security root of the wallet — losing or exposing it puts your balance at risk.

## Coldkey swap:

The process of transferring all state on a [coldkey](#coldkey) (balances, stakes, delegations) to a new coldkey. Initiated on-chain with a delay period before it finalises, to prevent theft via a compromised hot session. The pending swap is queryable via the pending-coldkey-swap API. See [Pending Coldkey Swap API](https://beta.taostats.io/docs/api-reference/pending-coldkey-swap).

## Commit Reveal:

Bittensor's approach to address [weight copying](#weight-copying). A process where validators encrypt their weights for a given period, preventing weight copiers from reading their weights immediately.

## Consensus:

Miner's score from the Yuma Consensus. Not applicable to validators.

## Consensus based weights:

See [liquid alpha](#liquid-alpha)

## Conviction:

A governance-vote weighting mechanism where locking tao for longer periods amplifies vote weight. Longer conviction locks give more influence over proposals. Conviction v2 refined the multipliers and lock schedule. See [Conviction v2](https://beta.taostats.io/docs/concepts/protocol-changes/conviction-v2).

## Daily Rewards:

A column in the subnet metagraph. Based on the current emission, extrapolated to 24 hours. Example: If your emission is 1 alpha/epoch, your Daily reward will be 20 alpha. (20 epochs/day)

## Delegate:

The verb form: to stake tao to a validator's [hotkey](#hotkey), creating a [delegation](#delegation) relationship. When tao is delegated, the owner of the tao receives a portion of the validator's emissions minus the validator's [take](#take). See [Delegation](https://beta.taostats.io/docs/understanding-taostats/accounts/delegation).

## Delegation:

The standing relationship in which a tao owner assigns stake to a validator's [hotkey](#hotkey). The delegator retains ownership via their [coldkey](#coldkey), the validator uses the stake weight for consensus, and the delegator earns a share of emissions minus the validator's [take](#take). "Delegate" (verb) is the act of creating this relationship; "delegation" is the relationship itself. See [Delegation](https://beta.taostats.io/docs/understanding-taostats/accounts/delegation).

## Deregistration:

Removal of a neuron from a subnet's [metagraph](#metagraph), freeing its slot for a new registration. Neuron deregistration occurs when a neuron with expired [immunity](#immunity) ranks lowest by incentive. Subnet deregistration can also occur, removing an entire subnet from the network. The deregistration ranking endpoint exposes the pending neuron order. See [Neuron Deregistration API](https://beta.taostats.io/docs/api-reference/subnet/get-subnet-neuron-deregistration).

## Dividends:

A score for validators denoting the fraction of emission for each validator.

## dTao:

The dynamic-tao protocol upgrade, activated February 2025, that replaced the root-subnet-weighted emission model with per-subnet automated market makers. Each subnet now has its own [alpha](#alpha) token traded against tao in a [liquidity pool](#liquidity-poolsubnet-pool), and emissions flow via pool activity rather than root-subnet weights. See [Subnet Mechanisms](https://beta.taostats.io/docs/concepts/subnets/subnet-mechanisms).

## Emission:

Emission describes the distribution of tao or [alpha](#alpha) in the network. Emission shows up in three contexts:

* **Subnet Emission**: the share of network tao that flows to each subnet. For example a 10% emission means that 10% of all tao generated is sent to that subnet. As of spec 440, this share is not a pure pro-rata of pool demand: an [emission gate](https://beta.taostats.io/docs/concepts/protocol-changes/emission-gate) redistributes emission from the low-demand tail to the above-bar winners.
* **Neuron Emission**: inside each subnet, all miners and validators are awarded emission (as seen in the [metagraph](#metagraph)). Neuron emission is denominated in the subnet's [alpha](#alpha) per [epoch](#epoch).
* **Alpha Emission**: the per-block issuance of a subnet's [alpha](#alpha) token, split between the pool, hotkeys, and the subnet owner per the subnet mechanism.

When a subnet closes registration, it retains its emission percentage, but all tao is [recycled](#recycle), so miners and validators receive no emission.

## Epoch:

A single cycle of the subnet [tempo](#tempo), during which validators set weights and emissions are distributed. Default tempo is 360 blocks, so an epoch is roughly 72 minutes at 12-second blocks. Rewards, [daily rewards](#daily-rewards) math, and Yuma consensus all key off epoch boundaries.

## Events:

Chain records emitted when an [extrinsic](#extrinsic) executes. Events cover registrations, stake additions/removals, delegations, transfers, weight commits, and governance actions. Taostats indexes chain events and exposes them via the events API. See [Events Detail](https://beta.taostats.io/docs/understanding-taostats/events/events-detail).

## Exchange rate:

This is defined by the ratio of tao\_in/alpha\_in ... the assets in the liquidity pool. Also known as [alpha price](#alpha-price).

## Extrinsic:

A transaction submitted to the [subtensor](#subtensor) chain. Extrinsics wrap one or more chain calls, are optionally signed by a [coldkey](#coldkey) or [hotkey](#hotkey), and produce [events](#events) when executed. Common examples: `Balances.transfer`, `SubtensorModule.add_stake`, `SubtensorModule.register_neuron`. See [Extrinsics and Events](https://beta.taostats.io/docs/concepts/chain-runtime/extrinsics-and-events).

## Finalized:

A block that has passed GRANDPA finality and can no longer be reverted. Distinct from "best block", which is the current head of the chain and may still reorganise. Taostats API responses generally reflect finalized state.

## Halving/Halvening:

When half of the remaining supply has been issued, the block reward drops by half. The first tao halving occurred in **December 2025**, when 10,500,000 tao had been issued; the block reward fell from 1 tao/block to 0.5 tao/block. Tao and alpha halve on independent schedules. See [Halving](https://beta.taostats.io/docs/concepts/tokenomics/halving).

## Hotkey:

Hotkeys are used to register subnets and nodes on the network. One hotkey can be registered per subnet. All hotkeys are associated with a coldkey, and a coldkey can have multiple hotkeys. The hotkey is the operational, online key — it signs the frequent network operations a running validator or miner performs, so it is kept accessible (hot). It cannot move the coldkey's funds, which limits the damage if it is compromised.

## Hyperparameter(s):

Per-subnet tunable parameters that govern subnet behaviour: tempo length, immunity period, minimum stake, weights-set rate limit, liquid-alpha toggle, and dozens more. Set by the subnet owner via `sudo_set_hyperparameter` extrinsics. See [Subnet Parameters](https://beta.taostats.io/docs/concepts/subnets/subnet-parameters).

## Identity:

On-chain identity records associated with a [coldkey](#coldkey), [hotkey](#hotkey), or subnet. Stores display name, website, description, and other metadata via the Identities storage in the SubtensorModule [pallet](#pallet). Surfaced across the API in owner and subnet responses.

## Immunity:

Time period (defined in blocks) that a new node or subnet is protected from de-registration.

## Incentive:

A score for miners. Calculated from consensus, the incentive denotes the portion of miner emissions to be distributed to each miner.

## Liquid Alpha:

Also known as consensus based weights. Introduced in Bittensor 7.3, this feature changes the way Validator dividends are calculated. The "Bond" between each validator and miner is an exponential moving average, where the most recent bond is weighted at alpha = 0.9. With Liquid alpha, this becomes a variable. Subnets with Liquid alpha enabled set the [Subnet Hyperparameters](https://beta.taostats.io/docs/concepts/subnets/subnet-parameters) `liquid_alpha_enabled` to true.

## Liquidity pool/Subnet pool:

Each subnet will have a liquidity pool where tao can be exchanged for alpha. The ratio of tao/alpha in the liquidity pool defines the tao/alpha exchange rate.

## MCP (Model Context Protocol):

An open standard for exposing tools and data to language models. Taostats runs an MCP server that lets LLM clients query subnet, neuron, price, and extrinsic data through structured tool calls. See [Model Context Protocol (MCP)](https://beta.taostats.io/docs/start-here/model-context-protocol-mcp).

## Mechanism (subnet mechanism):

A sub-subnet primitive introduced with [dTao](#dtao). A subnet owner can partition emissions and validation across multiple mechanisms inside the same subnet, each with its own scoring rules. Enables specialisation without registering a new subnet. See [Subnet Mechanisms](https://beta.taostats.io/docs/concepts/subnets/subnet-mechanisms).

## Metagraph:

The canonical per-subnet view of neurons and their scores at a given block. Contains one row per registered [neuron](#neuron) with columns for stake, incentive, dividends, trust, [vtrust](#vtrust), emission, and daily rewards. Taostats exposes the metagraph as an API endpoint and as a UI chart. See [Metagraph](https://beta.taostats.io/docs/understanding-taostats/subnets/metagraph).

## MEV / MEV shield:

Maximal extractable value: profit a block producer can capture by reordering or inserting transactions. Bittensor's MEV shield uses [commit reveal](#commit-reveal) and other primitives to keep validator weights hidden from potential extractors until after execution. See [MEV Shield](https://beta.taostats.io/docs/concepts/chain-runtime/mev-shield).

## Miner:

Miners are nodes on a subnet. Miners are given work to perform, and this work is graded by the validators. Miners receive alpha emissions (the subnet's token) as an incentive for their work. [Miner](https://beta.taostats.io/docs/concepts/miners/miner)

## Moving average:

A time-weighted average used in several Bittensor metrics. Notable uses: the bond exponential moving average in [Liquid Alpha](#liquid-alpha), and smoothed daily-reward projections in the metagraph. Not a standalone chain concept.

## Multisig:

A Substrate extrinsic pattern where a call requires signatures from M of N cosigners before it executes. Used for treasuries, subnet governance, and joint custody of large coldkey balances. Follows the standard Substrate multisig [pallet](#pallet) semantics. See [Multisig Extrinsics](https://beta.taostats.io/docs/understanding-taostats/extrinsics/multisig-extrinsics).

## Netuid:

The u16 identifier of a subnet on the [subtensor](#subtensor) chain. Every API endpoint that operates on a subnet takes `netuid` as its primary key. Netuid 0 is the [root subnet](#root-subnet). See [Subnets](https://beta.taostats.io/docs/understanding-taostats/subnets/subnets) and the [Subnet API](https://beta.taostats.io/docs/api-reference/subnet).

## Neuron:

A registered participant in a subnet, either a [validator](#validator) or a [miner](#miner). "Neuron" is the generic term when the validator/miner distinction does not matter, e.g. in the [metagraph](#metagraph) or in registration counts. Also referred to as "node" in some older docs. See the [Neuron API](https://beta.taostats.io/docs/api-reference/neuron).

## Nominator:

An alias for a delegator (see [Delegation](#delegation)) used in the "Calculating Nominator Returns" doc and in some Substrate contexts. Same on-chain relationship: tao owner assigning stake weight to a validator. Prefer "delegator" in new writing; keep "nominator" only when referencing existing docs or Substrate primitives.

## On-chain:

State that lives in the [subtensor](#subtensor) chain database and is settled by consensus. Contrasted with off-chain data (indexer views, API-side analytics, cached snapshots). If an answer changes based on which subtensor RPC you query, it is on-chain; if it comes from Taostats' indexer only, it is not.

## OTC:

The over-the-counter alpha marketplace on Taostats, where traders can execute alpha-token trades outside the on-chain AMM. Useful for size trades that would incur unacceptable [slippage](#slippage) against a subnet [liquidity pool](#liquidity-poolsubnet-pool). See the [OTC API](https://beta.taostats.io/docs/api-reference/otc).

## Pallet:

A Substrate module that packages related storage, extrinsics, and events. Bittensor's core logic lives in the `SubtensorModule` pallet, with supporting pallets for balances, staking, governance, and multisig. Extrinsic paths are namespaced by pallet, e.g. `SubtensorModule.register_neuron`.

## Parent hotkey:

A [hotkey](#hotkey) that delegates registration and validation authority to one or more [child hotkeys](#child-hotkey-childkey). The parent keeps stake; the child does the work. Used to separate long-lived stake custody from short-lived operational keys. See [Child & Parent Hotkeys](https://beta.taostats.io/docs/concepts/validators/child-hotkeys).

## Price impact:

The change in a subnet AMM's effective price caused by a single trade, expressed as a percentage of the pre-trade price. Larger trades against smaller pools produce larger price impact. Distinct from [slippage](#slippage), which measures the gap between expected and realised price for a specific order. See [Slippage](https://beta.taostats.io/docs/concepts/staking/slippage).

## Proxy:

A Substrate extrinsic pattern where one account calls on behalf of another via a delegated permission. Bittensor supports proxy for stake operations and governance votes, letting a "hot" operational account act for a "cold" ownership account without exposing coldkey signatures. See [Proxy Extrinsics](https://beta.taostats.io/docs/understanding-taostats/extrinsics/proxy-extrinsics).

## Rao:

The smallest denomination of [tao](#tao). One tao equals 10^9 rao. API responses that need integer precision typically report values in rao and let clients divide by 1e9 for display.

## Recycle:

Tao that is recycled is removed from circulation to be emitted again at a later date. As tao is recycled, the chain [halving](#halvinghalvening) is pushed to a later time. See [Recycling](https://beta.taostats.io/docs/concepts/tokenomics/recycling).

## Root subnet:

Subnet 0. Pre-[dTao](#dtao), root held the weighted vote that determined per-subnet emission shares. Post-dTao, root still exists for chain governance and legacy compatibility, but subnet emissions are driven by [liquidity pool](#liquidity-poolsubnet-pool) activity rather than root voting. See [Stakeholder Emissions: Root](https://beta.taostats.io/docs/concepts/how-emission-works/stakeholder-emissions-root).

## Runtime:

The Substrate runtime: the state-transition logic of the [subtensor](#subtensor) chain, versioned via `runtime_version`. Runtime upgrades ship as chain forkless updates that all nodes adopt automatically. [Extrinsic](#extrinsic) and [event](#events) schemas are pinned to runtime versions.

## Senate:

Bittensor's governance body, composed of the top-k validators by stake. The senate votes on proposals routed through the governance flow and can veto or approve chain changes. See [Senate](https://beta.taostats.io/docs/concepts/chain-runtime/senate).

## Signature:

A cryptographic signature (typically sr25519 or ed25519) that authorises a chain [extrinsic](#extrinsic). Produced by signing the encoded call with a [coldkey](#coldkey) or [hotkey](#hotkey). Wallets, browser extensions, and CLI tools all wrap this signing step.

## Slippage:

The gap between the price a trader expects and the price they actually receive on an AMM trade. Slippage is inversely related to [liquidity pool](#liquidity-poolsubnet-pool) depth: the shallower the pool, the larger the slippage for the same trade size. See [Slippage](https://beta.taostats.io/docs/concepts/staking/slippage).

## SS58:

The Substrate address encoding format used across Polkadot, Kusama, and Bittensor. An SS58 address is a base58-encoded public key with a network prefix byte and a checksum. Every wallet, coldkey, hotkey, and API sample in these docs uses SS58 strings. See the [SS58 spec](https://github.com/paritytech/ss58-registry).

## Stake:

A tao owner can stake (or delegate) their tao with a validator. The higher the validator's stake, the higher their return. Post-dTAO, delegated tao receives a portion of the subnet's alpha emissions (not TAO). See: [Delegation](https://beta.taostats.io/docs/understanding-taostats/accounts/delegation) and [Staking in dTao](https://beta.taostats.io/docs/concepts/staking/staking-in-dtao).

## Substrate:

The blockchain framework, maintained by Parity, that Bittensor's [subtensor](#subtensor) chain is built on. Substrate provides the runtime, consensus (BABE + GRANDPA), extrinsic model, and [pallet](#pallet) system. See [substrate.io](https://substrate.io/).

## Subnet:

Short for "subnetwork." Bittensor is made up of many subnets, each with its own purpose, token, and emissions; the count changes as subnets register and deregister — see the [live list on taostats.io/subnets](https://taostats.io/subnets). [Subnets](https://beta.taostats.io/docs/understanding-taostats/subnets/subnets).

## Subtensor:

The reference implementation of the Bittensor chain: the node software and runtime. "Subtensor" refers to the chain and its codebase; "Bittensor" refers to the broader network and its economic protocol. The two are commonly conflated but are distinct. See the [subtensor repo](https://github.com/opentensor/subtensor).

## Sudo:

A Substrate [pallet](#pallet) that grants a designated key privileged authority to execute otherwise-restricted extrinsics, typically used for governance and hyperparameter changes. On Bittensor, sudo calls originate from the governance flow, not from an individual account.

## Take:

The percentage of validator emissions kept by the validator. The remaining percentage is distributed amongst delegators. This is a variable that is set by each validator. It can range from 0-18% (default 18%) and can be updated once every 30 days.

## Tao:

The token of the Bittensor [subtensor](#subtensor). Since the December 2025 [halving](#halvinghalvening), 0.5 tao is emitted per block (12-second blocks). Tao can be divided into [rao](#rao) (there are 1B rao per tao). Learn more about [Tao](https://beta.taostats.io/docs/concepts/tokenomics/tao) and [Tao Emission](https://beta.taostats.io/docs/concepts/how-emission-works/tao-emission).

## tao in:

The tao in the subnet liquidity pool. It can also refer to the amount of tao being added to the pool in each block.

## Tempo:

The subnet parameter that sets how many blocks pass between weight-set windows and emission distributions. Default is 360 blocks, roughly 72 minutes at 12-second blocks. One tempo cycle is one [epoch](#epoch).

## Trust:

A score for miners, created by the Yuma Consensus. It is a combination of all the weights from all the validators. Higher trust leads to higher incentive & emissions.

## Undelegate:

The process of removing delegation/stake from a validator. The tao removed from the validator will be added to the user's coldkey.

## Unstake:

The inverse of [stake](#stake): remove tao (or alpha) from a hotkey and return it to the coldkey balance. Executed via `SubtensorModule.remove_stake`. Unstaking is subject to per-subnet rules and may involve unbonding delays on some flows.

## Validator:

Validators are nodes on a subnet. Validators check the work of the miners and grade the miners based on the quality of the response. [Validator](https://beta.taostats.io/docs/concepts/validators/validator)

## VTrust:

A score given to validators on a subnet. It is a ranking based on how well the validator's weights match the consensus. High VTrust leads to higher emissions.

## Weight copying:

When a validator copies the weights of other validators. This is sometimes done to avoid grading the miners, and thus not providing value to the Subnet.