Subnet Liquidity Pools

Subnet Liquidity Pools
Concept	Subnet pool reserves
Assets	TAO and alpha tokens
Used in	Staking and emissions
Scope	Not an exact amount source

Subnet liquidity pools are the paired-reserve context for subnet tokenomics in Bittensor. Each pool connects a TAO reserve with the subnet’s alpha-token reserve, giving the subnet a conversion surface for staking and unstaking (Understanding Subnets, Slippage).

The term belongs to reserve vocabulary. It names the pool structure and reserve relationship, not a static report of exact balances, a one-off balance snapshot, or a complete explanation of every tokenomics process connected to the pool.

Reserve Pair

A subnet pool has a TAO reserve and an alpha reserve. The TAO side connects the subnet to network-level TAO, while the alpha side connects the pool to the subnet-specific token context (Understanding Subnets, Glossary: TAO Reserve, Glossary: Alpha Reserve, Emission).

Those reserves are separate from alpha outstanding. Pool reserves describe what sits in the pool, while alpha outstanding describes alpha outside that reserve context.

The paired-reserve view is the reason the pool needs both sides. TAO reserve names the network-token side of the pool, alpha reserve names the subnet-token side, and subnet liquidity pool names the structure that holds the pair together (Understanding Subnets).

A pool statement is therefore pair-aware. A TAO reserve figure or alpha reserve figure can be useful on its own, but pool interpretation comes from reading the two reserve sides together.

Alpha outstanding sits outside that reserve view. That gives readers three nearby but distinct tokenomics ideas: TAO reserve, alpha reserve, and alpha outside the reserve (Glossary: Alpha Outstanding, Emission: Alpha outstanding injection).

Constant Product Context

The slippage documentation describes Bittensor subnet pools as constant product automated market maker pools. Staking and unstaking therefore pass through paired reserve behavior rather than a fixed one-sided conversion (Slippage).

That is why a conversion cannot be read from one side alone. A change involving one reserve is interpreted through the paired TAO and alpha reserve relationship.

Constant product context also explains why available pool depth matters. The reserve pair is the conversion surface for pool actions, so the resulting amount depends on the pool state used for that action.

This makes the pool different from an ordinary balance list. The reserve pair forms a conversion surface, so staking, unstaking, and slippage claims need pool context rather than a one-sided token description.

Staking and Unstaking Context

When TAO is staked into a subnet, the staking flow passes through the subnet pool reserve context and produces alpha-denominated stake. When stake is removed, alpha-denominated stake is converted back through the reserve system (Staking and Delegation, Glossary: Unstaking).

Staking and unstaking stay connected without becoming identical. Staking begins from TAO and creates subnet alpha stake, while unstaking moves in the opposite direction through the pool context.

The direction matters for interpretation. Staking starts from TAO entering subnet context; unstaking starts from alpha-denominated stake leaving subnet context through the reserve system (Staking and Delegation).

The pool remains the reserve surface through which the action passes; staking and delegation sources explain the user-facing staking model (Staking and Delegation).

Slippage Context

Slippage is the difference between a simple expected conversion and the result produced by the pool context used for the action (Slippage).

The important point is conceptual: pool reserves affect the resulting TAO or alpha amount. The amount belongs to the pool state used for that action.

Slippage language belongs with the pool action being discussed. The pool gives the conversion context; any observed example still needs the source for the amount being described.

Slippage is therefore adjacent to subnet liquidity pools but not identical to them. The pool is the reserve structure; slippage is the difference created when a conversion moves through that structure (Slippage, Understanding Subnets).

For readers, the pool answers where the conversion happens. Slippage answers how the conversion result can differ from a simple expectation because the reserve state changes during the action.

Emissions and Protocol Alpha

Bittensor emission documentation connects subnet pools to reserve injection. Emission flow can add TAO into subnet pool context, while the surrounding tokenomics model also separates TAO reserve, alpha reserve, and alpha-outstanding concepts (Emission, Emission: TAO reserve injection).

Protocol alpha is related to subnet pools but not the same term. Protocol alpha names protocol-owned alpha cached per subnet, while a subnet liquidity pool names the paired reserve structure (Glossary: Protocol Alpha).

That separation is useful because both terms can appear near reserve injection. Pool vocabulary names the reserve structure, while protocol-alpha vocabulary names a protocol-held alpha category.

Reserve injection concerns movement into subnet pool context. Flow-based emission language explains how TAO reserve injection is compared across subnets, while broader emissions pages explain how TAO and alpha rewards move through the network (Emission, Emission: Distribution Across Subnets).

This keeps emissions and pools connected without merging them. Emissions explain reward and reserve movement, while the subnet liquidity pool names the paired reserve surface affected by that movement.

Development Stage Context

The Introduction to Bittensor describes subnet development as moving from localnet to testnet and then mainnet. For Subnet Liquidity Pools, that sequence changes how an example should be read, because the surrounding network state differs at each stage.

In localnet, subnet Liquidity Pools can be exercised in an isolated development environment, where the surrounding chain state reflects local configuration rather than production history.

On testnet, subnet Liquidity Pools can be observed in a shared, non-production network whose state is kept separate from mainnet.

On mainnet, subnet Liquidity Pools applies on the live, production Bittensor network, where the surrounding state is real and persistent.

The Bittensor Networks reference separates mainnet, testnet, and localnet. A subnet Liquidity Pools example from one environment should not be read as representing another environment.

Relationship to Yuma Consensus

Subnet Liquidity Pools 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, subnet liquidity pools 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

Subnet liquidity pools are reserve and conversion vocabulary. They connect TAO reserves, alpha reserves, staking, unstaking, slippage, emissions, and protocol alpha into one pool-centered concept (Understanding Subnets, Slippage).

The stable point is that a subnet liquidity pool names the paired TAO and alpha reserve context for a subnet. Exact values, timing, or examples need the specific source that reports those values.

Alpha Outstanding Sits Outside Pool Reserves

Pool reserves describe what sits in the paired TAO and alpha reserve context, while alpha outstanding describes alpha outside that reserve context (Glossary: TAO Reserve, Glossary: Alpha Reserve).

That gives readers three nearby but distinct tokenomics ideas: TAO reserve, alpha reserve, and alpha outside the reserve.

Emission Injection Can Deepen Both Reserve Sides

Emission documentation describes reserve injection that adds TAO to the TAO reserve and matched alpha to the alpha reserve. Because both sides receive injected tokens, emission can deepen both reserves of a subnet’s pool together rather than only one side (Emission: TAO reserve injection, Emission: Alpha reserve injection).

That deepening changes reserve depth, not what the pool represents: it remains the same paired TAO-and-alpha reserve structure described above (Understanding Subnets).

Network Reading

Bittensor documentation separates localnet, testnet, and mainnet environments (Bittensor Networks, Introduction to Bittensor: Subnet development).

Subnet liquidity pool examples belong to the environment where they were observed. The pool concept is stable across contexts, while a localnet, testnet, or mainnet observation belongs to its own reserve history.