Slippage
Slippage is the gap between an expected amount and the amount received when a conversion moves through a pool (Glossary: Slippage, Understanding Slippage, Understanding Subnets).
In Bittensor, slippage can appear when staking or unstaking converts between TAO and subnet alpha tokens through subnet pool reserves. The term describes the conversion outcome, not a separate fee or token class.
In plain language, slippage answers what gap to expect between a pre-conversion estimate and the amount the pool returns. It is not a fee, a penalty charge, or a signal about subnet quality (Glossary: Slippage, Understanding Slippage).
Pool Conversion
Each Bittensor subnet has a TAO reserve and a subnet-specific alpha reserve. Those reserves form the pool setting for converting between network-level TAO and subnet-level alpha tokens (Understanding Subnets, Understanding Slippage).
The reserve pair is part of the evidence for any slippage claim. TAO reserve and alpha reserve describe the starting relationship, and the conversion changes that relationship as it moves through the pool.
Constant Product Mechanics
Slippage documentation describes subnet pools through constant-product mechanics. The reserve relationship changes as TAO or alpha moves through the pool, so staking and unstaking pass through a paired-reserve model rather than a fixed one-for-one conversion (Understanding Slippage, Understanding Subnets).
That model separates an estimate from the resulting amount. A pre-conversion quote is tied to the pool relationship before the action, while the received amount reflects the pool after the conversion has moved the reserves.
Conversion Size and Pool Liquidity
Slippage grows when the conversion is large relative to available pool liquidity. A larger movement through thinner reserves changes the reserve relationship more, widening the difference between the expected amount and the amount received (Understanding Slippage, Understanding Subnets).
The same amount can matter differently across pools. A movement that is small relative to one reserve pair can be larger relative to another, so slippage belongs with the selected subnet, pool liquidity, and conversion direction.
The practical question is whether the amount being converted is small or large relative to the subnet pool being used. Smaller movements through larger reserves leave the reserve relationship closer to its original state, narrowing the gap between expected and received.
That makes pool depth part of the reading. Slippage is not only about the requested amount; it is about that amount relative to the reserves available in the selected subnet pool (Understanding Slippage).
Staking and Unstaking
When TAO is staked into a subnet, the result is represented in that subnet’s alpha-token setting. Staking documentation describes subnet-local staking, and slippage documentation explains why the received amount can differ from a static expectation (Staking and delegation overview, Understanding Slippage).
The direction matters because staking moves TAO into a subnet pool and receives subnet-specific alpha-denominated stake. The expected and received amounts are interpreted through that direction.
Unstaking uses the same pool in the other direction. Alpha-denominated stake is expressed back into TAO terms through the subnet pool, so the received TAO amount can differ from a static expectation for the same reserve-based reason (Understanding Slippage, Staking and delegation overview).
Staking and unstaking therefore share one slippage concept even though the conversion direction is opposite. Both compare an expected amount with the amount received after the pool relationship has changed.
This keeps slippage separate from staking strategy. Staking and unstaking explain the action direction, while slippage explains the difference between expected and received amounts after that action moves through the pool.
Reserve Terms
Reserve ratio describes the pool relationship between TAO reserves and alpha reserves, while slippage describes the outcome difference when staking or unstaking moves through that relationship (Understanding Subnets, Understanding Slippage).
Alpha price sits beside the same reserve pair. It expresses the reserve relationship as a TAO-per-alpha quote, while slippage explains why using the pool can produce a different received amount after the reserve movement (Understanding Subnets, Understanding Slippage).
Reserve ratio, alpha price, and slippage all describe pool behavior from different angles. Reserve ratio and alpha price describe the relationship being used; slippage describes the conversion outcome after movement through that relationship.
The ordering matters for examples. Reserve ratio and alpha price can describe the pool before the conversion, while slippage describes what happened to the received amount after the conversion changed the reserve pair (Understanding Subnets, Understanding Slippage).
Price Protection
Price protection is adjacent to slippage because it controls how staking-related actions handle adverse price movement. Slippage describes the received-amount difference; price protection describes the response when movement exceeds tolerance (Price Protection, Understanding Slippage).
The two concepts are useful together, but they answer different questions. Slippage identifies the conversion effect. Price protection defines a response when the movement crosses a selected tolerance.
That pairing is enough for reference prose. Slippage explains the gap; price protection explains the tolerance response for staking and unstaking actions (Price Protection).
Development Stage Context
Mainnet, testnet, and localnet are separate environments for observed pool behavior (Bittensor Networks, Introduction to Bittensor: Subnet development, Understanding Slippage).
The slippage concept can be explained across those environments, but an observed example belongs to the network, subnet, and pool where it was measured. A local or testnet example is not production pool evidence.
Specific numbers need the network, subnet, pool state, and source that produced them. The slippage concept travels across environments; measured pool behavior belongs to one environment.
Relationship to Yuma Consensus
Slippage 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, slippage 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
Slippage is a pool-conversion outcome difference. It is not a staking recommendation, fixed amount, subnet quality claim, or operations guide (Glossary: Slippage, Staking and delegation overview).
The stable point is that slippage appears because Bittensor subnet activity uses pool reserves rather than a fixed one-for-one conversion. The term belongs with conversion direction, pool liquidity, and reserve movement.
Staking and Unstaking Move Reserves Through Pool Math
Official slippage documentation describes staking and unstaking as pool conversions that shift TAO and alpha reserves through the same constant-product relationship as swaps (Understanding Slippage, Staking and delegation overview).
Slippage therefore applies to delegation moves that change reserve balances, not only to explicit swap actions.
Price Protection Applies to the Trader Who Set Limits
Price Protection documentation describes limits a trader places on their own staking or unstaking order. When adverse pool movement exceeds that tolerance, the protection response applies to the order the trader configured rather than acting as a network-wide slippage cap (Understanding Slippage).
Slippage names the conversion gap; price protection names the trader-side tolerance response on a protected order.