Glossary
A
Active UID
A UID slot that is considered active within a specific subnet, allowing the associated hotkey to participate as a subnet validator or subnet miner.
See also: Subnet Miners, Subnet Validators
ADR (Alpha Distribution Ratio)
A metric that compares ALPHA tokens held by participants versus ALPHA tokens remaining in the AMM pool. ADR is calculated as the ratio of emissions to injections, measuring how much ALPHA goes to people (emissions) relative to how much is put into the pool (injections). A higher ADR means liquidation happens at a deeper discount to spot price. Under the current protocol, ADR tracks 2^(k - n), where k is the global TAO halving index and n is the subnet's ALPHA halving index.
Archive Node
A type of public subtensor node that stores the entire blockchain history, allowing for full data access and querying capabilities.
See also: Subtensor Nodes, Managing Subtensor Connections
Axon
A module in the Bittensor API that uses the FastAPI library to create and run API servers. Axons receive incoming Synapse objects. Typically, an Axon is the entry point advertised by a subnet miner on the Bittensor blockchain, allowing subnet validators to communicate with the miner.
See also: Subnet Miners, Subnet Validators
B
Bicameral Legislature
A two-tier legislative system comprising the Triumvirate and the Senate for proposal approval.
See also: Governance, Senate
Bittensor Wallet
A digital wallet that holds the core ownership in the Bittensor network and serves as the user's identity technology underlying all operations.
See also: Wallets, Working with Keys
Block
A unit of data in the Bittensor blockchain, containing a collection of transactions and a unique identifier (block hash). A single block is processed every 12 seconds in the Bittensor blockchain.
See also: Subtensor API
Blockchain validator
A node that participates in the Subtensor blockchain’s consensus mechanism to produce and validate blocks. Blockchain validators operate at the blockchain level, not within individual subnets.
Blockchain validator vs subnet validator
A blockchain validator participates in the network-wide consensus by validating transactions, producing blocks, and participating in network-wide consensus. In contrast, a subnet validator operates only within a specific subnet's consensus mechanism, where it evaluates miners' tasks and performances.
Blockchain validators function at the core consensus layer and affect the entire network, while subnet validators belong to the application layer and influence only local subnet incentives and rewards.
Burn cost
This refers to the required amount of TAO to be recycled when creating a new subnet, i.e., cost of registering a new subnet.
See also: Burn cost
C
Coldkey
A component of a Bittensor wallet responsible for securely storing funds and performing high-risk operations such as transfers and staking. It is encrypted on the user's device. This is analogous to a private key.
See also: Coldkey-Hotkey Security, Working with Keys
Coldkey-hotkey pair
A combination of two keys, a coldkey for secure storage and high-risk operations, and a hotkey for less secure operations and network interactions.
See also: Coldkey-Hotkey Security, Working with Keys
Commit Reveal
The Commit Reveal feature is designed to solve the weight-copying problem by giving would-be weight-copiers access only to stale weights. Copying stale weights should result in validators departing from consensus.
See also:
Consensus Score
The consensus score is calculated as the stake-weighted median of all weights assigned to a specific neuron by validators. This creates a consensus threshold that filters out outlier weights, ensuring that only weights near the median consensus are used in final rank calculations.
See also: Yuma Consensus, Consensus-Based Weights
Mathematical Definition:
For each neuron , the consensus score is calculated as:
Where:
- is the weight assigned by validator to neuron
- is the stake of validator
- is the consensus majority ratio (typically 51%)
- is the stake-weighted median function
Calculation Process:
- Weight collection: Gather all weights assigned to each neuron by validators
- Stake weighting: Apply stake weights to validator opinions
- Median calculation: Find stake-weighted median using κ parameter (typically 51%)
- Threshold establishment: Consensus score becomes clipping threshold for weights
Properties and Interpretation:
- Range: [0, 1] normalized values
- High Consensus: Values close to 1 indicate strong validator agreement
- Low Consensus: Values close to 0 indicate weak validator agreement
- Outlier Detection: Weights below consensus score are clipped to 0
Network Security Properties:
- Anti-Manipulation: Consensus filtering prevents weight manipulation by outliers
- Stake-Weighted: Higher stake validators have more influence in consensus
- Dynamic Threshold: Consensus adapts to changing network conditions
- Majority Rule: κ parameter controls consensus strictness (typically 51%)
Relationship to Other Metrics
Consensus vs Trust:
- Consensus: Stake-weighted median of weights (consensus threshold)
- Trust: Ratio of final rank to pre-rank (consensus alignment impact)
- Relationship: Consensus determines weight clipping, Trust measures the impact
Consensus vs Ranks:
- Consensus: Threshold for weight filtering
- Ranks: Final performance scores after consensus filtering
- Relationship: Consensus influences rank calculation through weight clipping
Consensus vs Validator Trust:
- Consensus: Per-neuron consensus thresholds
- Validator Trust: Sum of clipped weights set by each validator
- Relationship: Validator trust measures validator influence in consensus
Source:
bittensor/bittensor/core/metagraph.py:360-372subtensor/pallets/subtensor/src/epoch/run_epoch.rs:595
D
Delegate
A subnet validator that receives staked TAO tokens from delegators and performs validation tasks in one or more subnets.
See also: Delegation, Managing Stake with btcli
Delegate Stake
The amount of TAO staked by the delegate themselves.
See also: Managing Stake with btcli, Managing Stake with SDK
Delegation
Also known as staking, delegating TAO to a validator (who is thereby the delegate), increases the validator's stake and secure a validator permit.
See also: Delegation, Managing Stake with btcli
Dendrite
A client instance used by subnet validators and subnet miners to transmit information to axons on subnet miners and subnet validators. Dendrites communicate with axons using the server-client (Axon-dendrite) protocol.
See also: Subnet Miners, Subnet Validators
Deregistration
The process of removing a subnet miner or a subnet validator from the subnet due to poor performance.
See also: Miner Deregistration, Subnet Miners
Drand/time-lock encryption
Drand) is a distributed randomness beacon network that provides publicly verifiable, unpredictable, and unbiased random numbers. It is operated by the League of Entropy, a consortium of independent organizations running Drand nodes.
Drand provides time-lock encryption, a cryptographic technique that encrypts data so that it can only be decrypted after a specific time has passed. Drand provides this capability by regularly producing randomness "pulses" at fixed intervals. Data encrypted for a future Drand round cannot be decrypted—even by the person who encrypted it—until that round's randomness is published.
Key properties that make Drand suitable for applications in Bittensor, such as Commit Reveal:
- Decentralized: No single entity controls the randomness generation
- Verifiable: Anyone can verify that randomness was generated correctly
- Predictable timing: Pulses are produced at regular intervals
- Industry adoption: Used by multiple blockchain and cryptographic protocols
- Open source: Fully transparent implementation
Learn more:
E
EdDSA Cryptographic Keypairs
A cryptographic algorithm used to generate public and private key pairs for coldkeys and hotkeys in the Bittensor wallet.
See also: Working with Keys, Coldkey-Hotkey Security
Effective stake
The total staked TAO amount of a delegate, including their own TAO tokens and those delegated by nominators.
See also: Managing Stake with btcli, Managing Stake with SDK
Emission
Every block, TAO is injected into each subnet in Bittensor, and every tempo (or 360 blocks), it is extracted by participants (miners, validators, stakers, and subnet creators).
Emission is this process of generating and allocating currency to participants. The amount allocated to a given participant over some duration of time is also often referred to as 'their emissions' for the period.
Emissions are protected from manipulation through Exponential Moving Average (EMA) mechanisms that smooth both validator-miner bond evolution and subnet price effects.
See also: Emissions, Exponential Moving Average (EMA)
Encrypting the Hotkey
An optional security measure for the hotkey.
See also: Coldkey-Hotkey Security, Working with Keys
Epoch
An epoch in Bittensor is the period during which a subnet executes its consensus mechanism. Its is determined number of blocks defined by the subnet's tempo hyperparameter.
See also: Tempo, Yuma Consensus
Existential Deposit
The minimum amount of TAO required for an account to exist on the Bittensor blockchain. Accounts with balances below this threshold can be reaped (removed) to conserve network resources and prevent blockchain bloat from dust accounts.
The existential deposit is a runtime constant set in the Balances pallet configuration. While the default value is defined in the runtime code as 500 RAO (0.0000005 TAO), the actual on-chain value can be queried from the blockchain using the Balances::ExistentialDeposit constant.
Use the Bittensor SDK to query the current existential deposit:
import asyncio
import json
from bittensor.core.async_subtensor import AsyncSubtensor
from bittensor.utils.balance import Balance
async def main():
async with AsyncSubtensor(network="finney") as subtensor:
deposit = await subtensor.get_existential_deposit()
print(f"Existential deposit: {deposit.tao} TAO")
asyncio.run(main())
Exponential Moving Average (EMA)
A weighted moving average that prioritizes recent observations while exponentially decreasing the weight of older data points. In Bittensor, EMA is used in two critical stability mechanisms:
-
Validator-Miner Bond Smoothing: Smooths the evolution of bonds between validators and miners over time, rewarding early discovery while preventing abrupt manipulation attempts. Has two modes:
- Basic Mode: Single α ≈ 0.1 (~7-22 blocks for significant changes)
- Liquid Alpha Mode: Dynamic α range 0.7-0.9 based on consensus alignment (~1-13 blocks depending on consensus)
-
Subnet Flow Emission Smoothing: Protects emissions from manipulation by extremely slowly incorporating TAO flow changes (net staking minus unstaking) into emission calculations (α ≈ 0.000003209, ~30 day half-life, ~86.8 day effective window)
Formula: EMA(t) = α × Current_Value + (1 - α) × EMA(t-1)
Key Properties:
- Lower α = slower adaptation, higher stability
- Higher α = faster adaptation, lower stability
- Bittensor prioritizes stability with conservative α values
See also: Understanding Exponential Moving Averages, Consensus-based Weights, Validator-Miner Bonds, Emission
Existential deposit
An existential deposit is the minumum required TAO in a wallet (i.e., in a coldkey). If a wallet balance goes below the existential deposit, then this wallet account is deactivated and the remaining TAO in it is destroyed. This is set to 500 RAO for any Bittensor wallet.
See also What is the Existential Deposit?.
External Wallet
A Bittensor wallet created through the Bittensor website or using a tool like subkey, allowing users to use TAO without installing Bittensor.
See also: Wallets, Installation
F
Fast blocks
A development-only configuration that accelerates block production to 250ms intervals, enabling rapid local testing and immediate execution of on-chain operations.
See also: Create a local instance
H
Halving
The process where Bittensor's daily token emission rate cuts in half, similar to Bitcoin's halving mechanism. Halvings reduce the rate of new TAO tokens entering circulation.
Unlike Bitcoin which halves based on block numbers, Bittensor implements halvings based on total token supply. When specific supply thresholds are reached, the emission rate of TAO is cut in half.
The actual date of each halving is not fixed—it changes based on the amount of TAO being recycled each day.
See also:
- Halving countdown on TAO.app Tokenomics Dashboard
- Emission
Hotkey
A component of a Bittensor wallet responsible for less secure operations such as signing messages into the network, secure a UID slot in a subnet, running subnet miners and subnet validators in a subnet. It can be encrypted or unencrypted, but is unencrypted by default. The terms "account" and "hotkey" are used synonymously.
See also: Coldkey-Hotkey Security, Working with Keys
Hotkey-Coldkey Pair
Authentication mechanism for delegates and nominators and for delegates participating in the Senate.
See also: Coldkey-Hotkey Security, Working with Keys
I
Immunity Period
A grace period granted to newly registered neurons during which they are protected from deregistration due to poor performance. The immunity period allows new miners and validators time to establish themselves and improve their performance before becoming eligible for pruning. The default period being is 4096 blocks (~13.7 hours), but can be configured by the subnet creator.
See also: Miner Deregistration, Validator Deregistration, Subnet Hyperparameters
Incentives
A portion of the TAO emission received by the subnet miners when they provide valuable services and compete for UID slots in a subnet.
See also: Emissions, Anatomy of Incentive Mechanism
Incentive Mechanism
A system that drives the behavior of subnet miners and governs consensus among subnet validators in a Bittensor subnet. Each subnet has one or more incentive mechanisms, which should be designed carefully to promote desired behaviors and penalize undesired ones. When multiple incentive mechanisms are used, each operates independently with separate bond pools for Yuma Consensus calculations, allowing subnet creators to distribute emissions across different types of work or evaluation criteria.
See also: Anatomy of Incentive Mechanism, Multiple Incentive Mechanisms Within Subnets, Understanding Subnets
Issuance
The total amount of TAO circulating in the Bittensor network. Includes TAO that is held in wallets and subnet liquidity pools, as well as TAO that is locked as subnet registration fees.
This can be viewed on Bittensor explorers such as TAO.app's Tokenomics Dashboard, or TAOstats.
To query it directly from the chain, see: Subtensor Storage Query Example: Total Issuance
See also: Recycling, burning, and locking
L
Lite Node
A type of public subtensor node that stores limited blockchain data and relies on archive nodes for full historical data.
See also: Subtensor Nodes, Managing Subtensor Connections
Local Blockchain
A private blockchain used for developing and testing subnet incentive mechanisms. A local blockchain is not public and is isolated from any Bittensor network.
See also: Local Build, Create a Subnet
Local Wallet
A Bittensor wallet created on the user's machine, requiring the installation of Bittensor.
See also: Wallets, Installation
Loss Function
In the context of machine learning, a mathematical function that measures the difference between the predicted output and the ground truth. In Bittensor, incentive mechanisms act as loss functions that steer subnet miners towards desirable outcomes.
See also: Anatomy of Incentive Mechanism, Understanding Subnets
M
Mainchain
The primary Bittensor blockchain network, used for production purposes and connected to lite or archive nodes.
See also: Bittensor Networks, Subtensor Nodes
Mempool
The mempool is a temporary holding area in blockchain networks where pending and unconfirmed transactions sit before being included in a block. When you submit a transaction, it first enters the mempool, where it becomes visible to all network participants.
Metagraph
A data structure that contains comprehensive information about the current state of a subnet, including detailed information on all the nodes (neurons) such as subnet validator stakes and subnet weights in the subnet. Metagraph aids in calculating emissions.
See: The Subnet Metagraph
MEV (Maximal Extractable Value)
In blockchain networks, MEV refers to the profit that can be extracted by reordering, inserting, or censoring transactions within a block.
Common MEV attacks include:
- Front-running: Observing a pending transaction and submitting a similar transaction with higher priority to execute first
- Sandwich attacks: Placing transactions before and after a target transaction to profit from the price movement caused by that transaction
- Back-running: Submitting a transaction immediately after a target transaction to capitalize on its effects
In Bittensor, MEV attacks can affect staking and unstaking operations, where attackers might exploit knowledge of pending transactions to manipulate token prices. The MEV Shield feature protects against these attacks by encrypting transactions until they are included in a block.
See also: MEV Shield, Price Protection
Multiple Incentive Mechanisms
A feature that allows subnets to implement multiple independent evaluation systems within a single subnet. Each mechanism operates with its own bond pool for Yuma Consensus calculations, enabling subnet creators to distribute emissions across different types of work or evaluation criteria. Validators must evaluate miners separately for each mechanism, and miner performance in one mechanism does not affect their rating in another.
See also: Multiple Incentive Mechanisms Within Subnets, Anatomy of Incentive Mechanism
Miner Deregistration
The process of removing a poor-performing subnet miner from a UID slot, making room for a newly registered miner.
See also: Miner Deregistration
Mnemonic
A sequence of words used to regenerate keys, in case of loss, and restore coldkeys and hotkeys in the Bittensor wallet.
See also: Handle Seed Phrase, Working with Keys
N
NaCl Format
A secure encryption format, using the NaCl library, used for updating legacy Bittensor wallets to improve security.
See also: Working with Keys, Coldkey-Hotkey Security
Netuid
A unique identifier assigned to a subnet within the Bittensor network.
See also: Understanding Subnets, Working with Subnets
Neuron
The basic computing node in a Bittensor subnet, representing a node in a neural network. Neurons can be either subnet validators or subnet miners, each identified by a unique UID within their subnet and associated with a hotkey-coldkey pair for authentication and operations.
Neurons participate in the network through axon servers (miners) and dendrite clients (validators), exchanging synapse objects to perform subnet-specific tasks. Their performance is measured through metrics like rank, trust, consensus, and incentive scores, which determine emissions and validator permits.
See also: Understanding Neurons, Subnet Validators, Subnet Miners, NeuronInfo class
Nominate
The process of a staking TAO on a validator's hotkey. Nomination allows token holders to participate in subnet emissions by staking their TAO to active validators, earning proportional rewards based on the validator's performance.
See also: Staking and delegation
Nominator
An account that stakes TAO on a validator's hotkey. Nominators are token holders who nominate their TAO to validators/delegates to participate in subnet's consensus and earn dividends while keeping control of their tokens.
See also: Staking and delegation
Non-fast blocks
A development-only configuration that adheres to Subtensor’s default 12-second block interval, simulating production timing for features like delayed subnet activation.
See also: Create a local instance
O
Objective Function
In the context of machine learning and subnet operations, this refers to the goal that the subnet is continuously optimizing for, through its incentive mechanism.
See also: Anatomy of Incentive Mechanism, Understanding Subnets
P
Private Key
A private component of the cryptographic key pair, crucial for securing and authorizing transactions and operations within the Bittensor network.
See also: Working with Keys, Coldkey-Hotkey Security
Proposal
A suggestion or plan put forward by the Triumvirate for the Senate to vote on.
See also: Governance, Senate
Proposal hash
A unique identifier for a proposal used in the voting process.
See also: Governance, Senate
Public Key
A cryptographic key that is publicly available and used for verifying signatures, encrypting messages, and identifying accounts in the Bittensor network. This is the publicly shareable part of the cryptographic key pair associated with both the coldkey and hotkey, allowing others to securely interact with the wallet.
See also: Working with Keys, Coldkey-Hotkey Security
Public Subtensor
A publicly accessible node in the Bittensor network that can be run as a lite node or an archive node and synchronized with either the mainchain or testchain.
See also: Subtensor Nodes, Managing Subtensor Connections
R
RAO
A denomination of TAO, representing one billionth (10-9) of a TAO.
See also: Emissions
Rank
This metagraph property represents the final aggregate judgment of a each miner, computed by Yuma Consensus alogirithm operating over the miner-ratings submitted by a subnet's validators each tempo. The final rank score represent a miner's performance after any outlier weights set by validators have been removed through consensus clipping. This ensures that only weights near the median consensus are used in final calculations.
Ranks are calculated as the stake-weighted sum of consensus-clipped weights and directly determine emissions to miners.
See also: Emissions, Yuma Consensus, Subnet Metagraph
Relationship to Other Metrics:
- Ranks vs Consensus: Ranks are calculated using consensus-clipped weights
- Ranks vs Trust: Trust measures how much consensus clipping affected the rank
- Ranks vs Incentive: Ranks are normalized to become incentive values
- Ranks vs Validator Trust: Validator trust measures validator influence in consensus
Calculation Process:
- Pre-ranks: Initial stake-weighted sum of all weights before consensus filtering
- Consensus calculation: Stake-weighted median of weights per neuron (consensus threshold)
- Weight clipping: Weights clipped at consensus threshold to remove outliers
- Final ranks: Stake-weighted sum of clipped weights (the rank value)
Properties and Interpretation:
- Range: [0, 1] normalized values after final normalization
- High Rank: Values close to 1 indicate strong consensus-based performance
- Low Rank: Values close to 0 indicate weak consensus-based performance
- Incentive Distribution: Ranks directly determine incentive allocation to miner neurons
Network Security Properties:
- Consensus-Based: Ranks reflect network consensus rather than individual validator opinions
- Outlier Protection: Consensus clipping prevents manipulation by outlier weights
- Stake-Weighted: Higher stake validators have more influence in rank calculation
- Dynamic Updates: Ranks are recalculated every epoch based on current network state
Mathematical Definition: For each neuron , the rank is calculated as:
Where:
- is the stake of validator