Moving Stake
Moving stake is the operation of moving a staked position between hotkeys and/or between subnets in a single atomic transaction, without first withdrawing to the coldkey. The Staking and delegation overview lists it alongside transferring stake and direct unstaking as one of the participant-facing ways to rearrange an existing staked position.
In Taopedia terms, moving stake names a delegation-change operation that can move a staked position between hotkeys and/or between subnets. It belongs alongside staking (adding stake), unstaking (withdrawing stake), and transferring stake (reassigning coldkey ownership) as one of the core stake-management operations.
In plain language, moving stake answers what changes when a participant redirects an existing staked position: the hotkey, the subnet, or both, without a separate withdrawal step. The operation keeps the staked exposure active while re-pointing it to a new hotkey or subnet target (Glossary: Stake).
Why Moving Stake Exists
A participant may need to redelegate an existing staked position to a different hotkey or subnet — for example, when shifting support between validators, reorganizing hotkey allocation, or responding to changing validator performance. The Staking and delegation overview describes moving stake as a participant-facing alternative to unstaking and restaking under a different hotkey or subnet.
Atomic Rearrangement in One Transaction
Moving stake is atomic in the sense that the participant rearranges an existing delegated position without first withdrawing TAO to the coldkey and staking again in a separate step. The Staking and delegation overview lists moving stake alongside transferring stake and unstaking as ways to change how stake is held, but moving stake specifically re-points delegation rather than changing coldkey ownership or fully withdrawing from delegation.
That matters when a participant wants continuity of delegated exposure. Unstake-and-restake passes through the coldkey in between, which can change timing, fee exposure, and the sequence of pool conversions involved. Moving stake keeps the rearrangement inside one submitted stake-management action aimed at a new hotkey target, a new subnet target, or both.
Reference: Staking and delegation overview
For a reader, the distinction from unstaking matters when timing or pool effects are relevant. Moving stake keeps the position active across one submitted action, while unstaking and restaking means the amount passes through the coldkey and re-enters the pool through a second separate conversion.
When Moving Stake Fits Better Than Unstaking
Unstaking is the right concept when the goal is to stop delegating and bring stake back under direct coldkey control. Moving stake is the better fit when the goal is to change where the stake is delegated while keeping it delegated. A participant shifting support from one validator hotkey to another on the same subnet, or moving delegated exposure from one subnet market to another, is rearranging the delegation target rather than exiting delegation entirely.
The official overview presents moving stake as an alternative to unstaking and restaking under a different hotkey or subnet. For readers, the decision boundary is intent: withdraw to the coldkey versus redelegate in place. Mixing the two ideas can make stake-management plans harder to read, because unstaking ends delegation while moving stake preserves it under new targets.
References: Staking and delegation overview, Glossary: Unstaking
Conversion and Fee Boundaries
Moving stake still interacts with Bittensor’s staking and pool-conversion context even though it is not the same operation as unstaking. Stake rearrangements can involve conversion behavior, slippage, and transaction fees depending on the path and network state at submission time. Taopedia articles at concept level should not quote live fees or promise a particular conversion outcome.
The useful reader boundary is that moving stake names a delegation rearrangement operation, not a fee quote or slippage guarantee. Participants evaluating a move should read official staking documentation and current network conditions for operational detail rather than treating this article as a step-by-step movement guide. Moving stake remains a normal stake-management concept whose exact behavior belongs in official references and live chain state.
References: Staking and delegation overview, Understanding Slippage, Transaction Fees in Bittensor
Relationship to Staking
Staking adds new TAO to a validator’s hotkey on a subnet; moving stake rearranges stake that is already delegated, re-pointing the delegation to a different hotkey and/or subnet. The Glossary: Staking describes staking as attaching TAO to a validator hotkey, while moving stake re-points an existing attachment to a different hotkey and/or subnet.
Relationship to Unstaking
Unstaking withdraws stake back to the coldkey so it is no longer delegated; moving stake changes which hotkey and/or subnet the stake is delegated to without withdrawing it. A participant who wants TAO back in the coldkey must unstake; a participant who wants a different hotkey or subnet to hold the position can move.
Relationship to Transferring Stake
Transferring stake changes which coldkey owns the stake; moving stake changes which hotkey and/or subnet the stake sits on. The Staking and delegation overview describes both as stake-rearrangement operations, but they act at different levels of the wallet model — one changes the owner, the other changes the delegation target.
Relationship to Hotkey
The hotkey is one of the dimensions that moving stake can change. The Glossary: Hotkey describes a hotkey as the operational key that runs a validator and holds its delegated stake, and moving stake can reassign a staked position from one hotkey to another.
Relationship to Subnet
The subnet is the other dimension that moving stake can change. The Glossary: Subnet describes a subnet as the incentive-based competition market that holds a staked position, and moving stake can reassign a staked position from one subnet to another.
Relationship to Autostaking
Moving stake and autostaking address related but different parts of Bittensor staking position management. Moving stake is an operation that atomically transfers an existing delegated stake position from one hotkey or subnet to another in a single transaction, without first withdrawing to the coldkey. Autostaking is a mechanism that automatically routes a miner’s emission proceeds into a staking position on a chosen validator, accumulating delegated stake over time as emissions arrive. The Staking and delegation overview describes moving stake as an atomic rearrangement of an existing position, and the Autostaking documentation describes autostaking as automatically staking a miner’s emissions to a chosen validator.
Autostaking accumulates a staked position by adding emission proceeds over time; moving stake repositions an already-accumulated position without withdrawing from it. A miner who has enabled autostaking and grown a staking position on one validator could later use moving stake to repoint that position to a different validator hotkey or subnet — consolidating or rebalancing staking exposure — without the withdrawal and re-staking steps that would otherwise be needed. Autostaking creates and grows the position; moving stake changes where an existing position sits.
References: Staking and delegation overview, Autostaking
Relationship to Coldkey Swap
Moving stake and coldkey swap are related but distinct stake-management operations in Bittensor vocabulary. Moving stake is the atomic rearrangement of an existing delegated position from one hotkey or subnet to another without first withdrawing to the coldkey, while coldkey swap is the staged migration of the entire wallet’s on-chain identity — TAO balances, subnet ownership, and registrations — to a new coldkey. The Staking and delegation overview describes moving stake as a participant-facing rearrangement operation, and the Rotate or Swap your Coldkey documentation describes coldkey swap as the identity-migration operation that re-homes everything the old coldkey controlled.
For readers, moving stake changes where a delegated position sits while keeping the coldkey and wallet identity unchanged, while coldkey swap changes the controlling coldkey itself. The two are not interchangeable: moving stake re-points the delegation target of an existing staked position, coldkey swap migrates the entire on-chain identity to a new key pair. A participant who wants to rebalance validator support can use moving stake; a participant who needs to replace a compromised controlling key uses coldkey swap.
References: Staking and delegation overview, Rotate or Swap your Coldkey
Relationship to Conviction and Locked Stake
Moving stake and conviction both act on an existing staked position, but they describe different things. Moving stake is the operation of relocating a staked position between hotkeys and/or between subnets in a single atomic transaction, as the Staking and delegation overview describes. Conviction and locked stake, by the Conviction and locked stake documentation, describe locking subnet alpha stake so that it builds a time-based commitment score and the staked balance cannot be silently reduced below the locked amount.
For readers, moving stake answers how a position is relocated, while conviction answers whether part of a position has been locked for commitment. The two are not interchangeable: moving stake changes where stake sits, whereas conviction places a lock on staked alpha that resists reduction. Because a lock keeps the balance from dropping below the locked amount, a conviction lock constrains how much of a position moving stake could take out of that subnet — the lock and the relocation operation act on the same position from different directions.
References: Staking and delegation overview: Moving stake, Conviction and locked stake
Relationship to Yuma Consensus
Moving Stake 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, moving stake 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
This article defines moving stake as a concept. It does not describe movement steps, recommend when to move stake, or state current fee, slippage, or fee-minimization behavior. Readers should use the official staking documentation for operational detail.
Development Stage Context
The Introduction to Bittensor describes subnet development as moving from localnet to testnet and then mainnet. For moving stake, that sequence changes how readers should interpret evidence about cross-subnet staking operations and their effects on pool reserves.
In localnet, stake movement can be tested in an isolated environment. Pool reserve changes and slippage in localnet reflect local configuration and do not represent production subnet pool state.
On testnet, moving stake can be observed in a shared, non-production environment. Testnet stake moves affect testnet subnet pools but are separate from mainnet staking state and validator associations.
On mainnet, moving stake is a live Subtensor operation that changes TAO and alpha positions across actual subnet pools. The Staking and delegation overview describes how stake movement interactions with pool reserves operate on the production network.
The Bittensor Networks reference separates mainnet, testnet, and localnet. A stake movement example from one environment should not be read as representing pool state or staking associations in another environment.
For readers, this keeps moving stake examples grounded in their network context. Localnet, testnet, and mainnet each have separate pool histories, so stake movement belongs to the specific network where it was submitted.
Moving Stake Re-Points Delegation Without Unstaking
The Staking and delegation overview lists moving stake as a way to rearrange an existing delegated position without first withdrawing TAO to the coldkey. The operation changes which hotkey and/or netuid holds the stake while keeping delegation active.
That distinction matters when comparing move to unstaking. Unstaking ends delegation; moving stake redirects it inside one submitted stake-management action.
Cross-Subnet Moves Change the Selected netuid
Official delegation material treats staking as local to a subnet. Moving stake between subnets therefore changes which subnet market holds the delegated position, such as moving support from one netuid to another, rather than relabeling the same global pool entry.
Readers should attach the destination netuid when describing a cross-subnet move. Delegation rewards, pool reserves, and alpha-denominated stake records follow the subnet where the stake was placed (Understanding Subnets).
Pool Conversions Can Still Apply to Stake Moves
Understanding Slippage describes staking and unstaking as conversions through subnet pool reserves. Moving stake can therefore interact with the same pool mechanics as other stake-management actions on an alpha subnet, even though the article does not quote live fees or slippage outcomes.
Moving stake names the delegation rearrangement concept; slippage and transaction fees belong to operational references for the specific path and network state at submission time.