Price Protection
Price protection is Bittensor’s guardrail for adverse price movement during staking-related activity. It is most relevant around staking and unstaking through subnet pools (Glossary: Price Protection, Price Protection, Understanding Slippage).
The concept sits between pool mechanics and price-movement handling. Slippage explains why a received amount can differ from an expectation; price protection defines how much adverse movement a staking or unstaking action is allowed to tolerate.
What It Does
Price protection applies to adverse price movement while staking or unstaking through subnet pools. It checks movement against a selected tolerance, then determines whether the staking or unstaking action continues (Price Protection, Understanding Slippage).
The term is not a general promise that a pool price will stay fixed. It describes how Bittensor handles price movement when a staking or unstaking action reaches the pool.
This makes the concept practical but narrow. Price protection can limit adverse movement handling, but it does not remove slippage, quote a final amount, or replace broader staking and fee references (Transaction Fees in Bittensor).
Strict, Partial, and Unsafe
Price protection has three choices: strict, partial, and unsafe. Strict protection rejects the action when price movement exceeds tolerance. Partial protection limits the action to the part that remains within tolerance. Unsafe proceeds without that protection (Price Protection).
Those choices describe outcome handling. They are not separate staking strategies and they do not change the meaning of slippage; they determine how the action responds after adverse movement is measured (Price Protection, Understanding Slippage).
Tolerance and Outcomes
Tolerance is the allowed adverse movement for the action. Slippage explains why pool conversions can produce a different received amount, while price protection explains how the action reacts when that difference is outside tolerance (Price Protection, Understanding Slippage).
That distinction keeps the page focused on the useful reading: price protection is about reaction to adverse pool movement, not a guarantee that the received amount will match an initial expectation (Price Protection).
Pending Pool Movement
Pool conditions can change while a staking or unstaking action is pending or being processed. Price protection compares movement across that interval rather than assuming the initial pool state is unchanged (Price Protection, Understanding Slippage).
Concrete examples need the staking direction, selected tolerance, protection choice, pool state, and network where the action occurs. Without those details, a numeric price-protection example can be too broad for pool-specific behavior.
Slippage and Nearby Risks
Slippage is the difference between expected and received amounts during Bittensor pool conversions. Price protection responds to that kind of movement when it exceeds tolerance (Understanding Slippage, Price Protection).
Price protection and MEV Shield address different parts of the same risk area. MEV Shield hides sensitive pending details before block inclusion, while price protection controls how staking and unstaking actions handle adverse price movement (MEV Shield, Price Protection).
Fees are also separate. Fee references explain network costs, while price protection explains tolerance for pool-price movement (Transaction Fees in Bittensor).
Development Stage Context
Bittensor separates mainnet, testnet, and localnet environments. Price-protection examples belong to the network where the pool movement is observed (Bittensor Networks, Introduction to Bittensor: Subnet development).
Local examples can explain mechanics in isolation. Testnet examples belong to shared non-production state. Mainnet examples belong to production chain history. Those environments do not share one pool-state record.
Specific numbers or outcomes need the network and pool state that produced them. The general concept travels across environments; the measured result belongs to one environment.
Relationship to Yuma Consensus
Price Protection 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, price protection 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
Price protection does not name a fixed pool price, a slippage calculator, MEV Shield, or a guarantee that the received amount will match an initial expectation (Price Protection, Understanding Slippage).
Use the term for how a staking or unstaking action reacts when measured pool movement exceeds the trader’s selected tolerance on their own order.
Price Protection Limits Losses But Does Not Hide Pending Trades
Official Managing Your Stakes documentation states that price protection caps how much adverse price movement a staking or unstaking action will accept. The same guidance states that price protection does not prevent sandwich attacks entirely, while MEV Shield hides sensitive pending transaction contents until block inclusion.
Price protection therefore reacts when movement is measured at execution time. It does not stop another party from seeing a pending stake or unstake in the mempool and ordering around it (Price Protection).
Staking In and Unstaking Out Can Both Use Price Protection
The Glossary: Price Protection applies to adverse price movement during staking-related activity through subnet pools. The Glossary: Staking and Glossary: Unstaking entries both note that Bittensor provides price-protection mechanisms for those conversions.
Whether TAO moves into a subnet pool or alpha moves back out, price protection names how much measured movement the action will tolerate once the pool shift is known (Understanding Slippage).
Slippage Describes the Pool Move Price Protection Reacts To
Slippage is the difference between expected and received amounts when a conversion moves through subnet pool reserves. Price protection compares measured movement against a selected tolerance after that slippage appears, then applies strict, partial, or unsafe handling according to the chosen setting (Price Protection).
Slippage vocabulary explains why the received amount can differ from an estimate. Price protection vocabulary explains what happens once that difference is measured during staking or unstaking (Understanding Slippage).