Liquidity Positions
Liquidity positions are range-based liquidity commitments for Bittensor subnet pools. They supply liquidity for a selected subnet across a selected range (User Liquidity Positions).
The concept belongs to subnet tokenomics. It is about supplying depth to a TAO-and-alpha pool, not about mining, validation, or subnet work evaluation.
In plain language, liquidity positions answers who supplies range-based depth to a subnet pool and under what range condition. It is not a staking position with a validator, a mining role, or a subnet governance action (Glossary: Liquidity Positions).
The distinction from staking matters. Staking attaches TAO or alpha support through a subnet’s delegation model; a liquidity position supplies depth to the subnet pool for conversion use. Both involve subnet assets, but the role is different.
Pool Role
Bittensor subnets use liquidity pools with TAO and subnet alpha sides (Understanding Subnets: Liquidity pools).
A liquidity position is a contribution inside that pool setting. It adds range-based liquidity to a subnet pool rather than replacing the pool’s reserve structure.
That means liquidity-position vocabulary starts from the same TAO-and-alpha pool described by the subnet reserve model. TAO reserve and alpha reserve describe the pool sides; liquidity position describes supplied depth around that pool (Understanding Subnets: Liquidity pools).
This makes liquidity positions pool-depth terms rather than reward-role terms. The position belongs to the pool structure, while mining, validation, and staking describe other subnet roles (Understanding Subnets: Liquidity pools).
That pool role also separates liquidity positions from simply holding TAO or alpha. Holding an asset describes ownership; a liquidity position describes range-based depth supplied to the subnet pool (User Liquidity Positions).
Range-Based Supply
Liquidity positions use concentrated liquidity. The liquidity-position reference explains that a position is supplied over a selected range (User Liquidity Positions).
That makes the term range-sensitive. A liquidity position is not just a generic balance in a pool; it is liquidity supplied under a range condition.
The range also makes the term different from simply holding TAO or alpha. A position describes liquidity committed to the pool under the selected range model (User Liquidity Positions).
The selected range is part of the position’s meaning. Without the pool and range, the phrase does not say enough about where the liquidity sits or when it contributes depth.
Range wording therefore belongs with the position itself. A claim about a liquidity position is clearer when it keeps the subnet pool, supplied depth, and selected range together (User Liquidity Positions, Understanding Subnets: Liquidity pools).
Staking Contrast
Liquidity positions and staking answer different questions. The liquidity-position reference separates liquidity provision from staking (Liquidity Positions vs. Staking).
Staking supports validator-related subnet participation. A liquidity position supports pool depth for TAO-and-alpha subnet liquidity. Both can involve TAO and alpha, but they are different concepts.
This contrast prevents every TAO-and-alpha action from being treated as staking. Staking belongs to validator support, while liquidity positions belong to pool-depth support inside the subnet liquidity model (Liquidity Positions vs. Staking).
Slippage and Fees
Liquidity positions are related to slippage because both concern available pool depth. Slippage describes how pool depth affects swap outcomes (Slippage).
The liquidity-position reference also discusses fees for subnet pool activity inside the selected range (User Liquidity Positions).
Slippage and fee behavior depend on pool depth, range, and activity. The concept does not promise an outcome for any specific subnet, range, or amount of supplied liquidity.
Slippage and fees stay attached to pool depth and range conditions. They do not turn a liquidity position into a staking position or a subnet quality claim (Slippage).
Reserve Terms
Liquidity positions sit around the subnet reserve pair. TAO reserve names the pool-held TAO side, and alpha reserve names the paired subnet-alpha side (Understanding Subnets: Liquidity pools, Emission: Alpha reserve injection).
That reserve pair is the pool setting. A liquidity position adds range-based depth around the pool; it does not rename either reserve side.
This keeps reserve vocabulary and supplied-liquidity vocabulary separate. The reserve pair names the pool structure, while the liquidity position names a contribution within that structure.
The same distinction keeps liquidity-position language separate from reserve-ratio language. Reserve ratio compares pool sides; liquidity position describes range-based depth supplied around those sides.
Development Stage Context
The Introduction to Bittensor describes subnet development as moving from localnet to testnet and then mainnet. Mainnet, testnet, and localnet are separate environments for observed pool data (Bittensor Networks).
The liquidity-position concept can be explained across those environments, but an observed liquidity-position example belongs to the network and subnet where it was observed.
Localnet examples can test range-based supply in isolation. Testnet examples add shared non-production pool state. Mainnet liquidity-position interpretation concerns production subnet pools on the active network.
Relationship to Yuma Consensus
Liquidity Positions and Yuma Consensus describe related parts of Bittensor’s incentive system. Yuma Consensus is the on-chain process that aggregates validator weight signals within a subnet into miner incentives and validator dividends, applying consensus clipping, bonding, and emission calculation (Yuma Consensus).
For readers, liquidity positions names a specific part of that incentive picture, while Yuma Consensus names the consensus process that turns validator weights into the resulting incentives and dividends.
Reader Boundary
Liquidity positions are range-based liquidity commitments inside subnet pools (User Liquidity Positions). They are not an earnings promise, staking guide, subnet quality signal, or operator procedure.
When the focus is validator support, staking is the more precise concept. When the focus is pool depth and range-based liquidity, liquidity position is the more precise term.
Coldkey and Hotkey Each Supply a Side
Creating a liquidity position draws from two wallet roles rather than one balance. Official liquidity-position documentation states that TAO are taken from the user’s coldkey, while alpha tokens are taken from the hotkey on which the position was created, and both sides are locked in the position (User Liquidity Positions).
That split keeps fund custody and subnet operational stake on separate keys. A holder may supply TAO from coldkey custody while the paired alpha side comes from hotkey stake already associated with the subnet where the position lives.
The same rule applies when modifying a position. Adding or removing liquidity uses the same token composition formula as creation, so both keys can be involved again depending on the current subnet price and selected range (User Liquidity Positions: Modifying a Position).
References: User Liquidity Positions, Glossary: Coldkey
Subnet Price Sets the Token Mix
A liquidity position can hold TAO, alpha, or both at once, and the mix depends on where the subnet token price sits relative to the position’s low and high bounds (User Liquidity Positions: Dynamic token composition).
When price falls below the range, the position becomes entirely alpha. When price rises above the range, it becomes entirely TAO. When price sits inside the range, the position keeps a mixed composition of both tokens.
That behavior is not cosmetic. The same price-versus-range relationship decides which tokens are required when a position is created, which tokens return when liquidity is removed, and how fee accrual interacts with the position at different life-cycle stages (Managing User Liquidity Positions Tutorial).
References: User Liquidity Positions: Dynamic token composition, Managing User Liquidity Positions Tutorial
Fees Require an Active Withdrawal Step
Liquidity-position fees are not paid out on the same tempo cadence as emission rewards. Official guidance states that fees accumulate when others stake or unstake within the position’s price range, but they are tracked separately from the position’s supplied liquidity and reach the wallet only when the creator modifies or removes the position (User Liquidity Positions: Fee Distribution).
That collection rule differs from passive holding. A position can be earning fees while those fees remain locked until the creator performs one of those withdrawal actions.
The same documentation also notes that a position does not accumulate fees from staking operations performed by the coldkey that owns it. Fee vocabulary therefore names activity by other participants inside the defined range, not every stake action tied to the same wallet pair (User Liquidity Positions).
References: User Liquidity Positions: Fee Distribution, User Liquidity Positions: Fee Accumulation