Transferring Stake
Transferring stake is the operation of changing which coldkey owns a staked position. The Staking and delegation overview lists it alongside moving stake and direct unstaking as one of the participant-facing ways to rearrange an existing staked position.
In Taopedia terms, transferring stake names an ownership-change operation. It belongs alongside staking (adding stake), unstaking (withdrawing stake), and moving stake (rearranging between hotkeys) as one of the core stake-management operations.
Why Transferring Stake Exists
A participant may need to reassign a staked position to a different coldkey — for example, when migrating to a new coldkey or reorganizing wallet custody. The Staking and delegation overview places transferring stake as a participant-facing alternative to unstaking and restaking from the new coldkey.
What Ownership Changes Without Unstaking
Transferring stake reassigns coldkey ownership over a delegated position that remains staked. The Staking and delegation overview lists transferring stake alongside moving stake and direct unstaking as ways to rearrange an existing position, but transferring stake specifically changes which coldkey owns the stake rather than withdrawing it to an unstaked balance. The validator hotkey receiving the delegation can stay the same while ownership moves.
Readers should not treat transferring stake as an automatic withdrawal. Unstaking returns stake to the coldkey as unstaked TAO or converted alpha proceeds; transferring stake moves ownership of the still-delegated position to another coldkey. Operational fees, conversion paths, and command details belong in official staking documentation rather than in this concept definition.
References: Staking and delegation overview, Glossary: Coldkey
Validator Target Unchanged During Transfer
Moving stake changes which hotkey or subnet holds a delegated position; transferring stake changes which coldkey owns that position. The staking overview treats both as rearrangement operations, but they act at different layers of the wallet model. A transfer can leave the same validator hotkey in place while the owning coldkey changes, which is why the two operations answer different participant questions.
For readers deciding between operations, moving stake re-points delegation; transferring stake reassigns ownership. A participant who wants a different validator target should look to moving stake or unstaking rather than assuming a transfer changes the hotkey destination.
References: Staking and delegation overview, Glossary: Hotkey
When Transfer Fits Better Than Coldkey Swap
Transferring stake and coldkey swap both involve coldkey ownership, but at different scopes. The staking overview describes transferring stake as changing ownership of one staked position, while Coldkey Swap documentation describes moving an entire on-chain identity to a new coldkey while preserving associated hotkeys and subnet registrations. A targeted stake transfer can reassign one delegated amount without migrating every registration tied to the wallet hierarchy.
Readers comparing custody changes should match the operation to the scope of what must move. Transfer fits when only one staked position should change owner; coldkey swap fits when the participant needs the broader identity migration described in official coldkey swap material. Neither operation replaces careful coldkey and hotkey protection during custody changes.
References: Staking and delegation overview, Coldkey Swap
Relationship to Staking
Staking adds new TAO to a validator; transferring stake reassigns ownership of stake that is already there. The Glossary: Staking describes staking as attaching TAO to a validator hotkey, while transferring stake changes which coldkey owns that attachment.
Relationship to Unstaking
Unstaking withdraws stake back to the coldkey so it is no longer delegated; transferring stake moves the ownership of the staked position to a different coldkey without withdrawing it. A participant who wants TAO back must unstake; a participant who wants a different coldkey to own the position can transfer.
Relationship to Moving Stake
Moving stake changes which hotkey the stake sits on; transferring stake changes which coldkey owns the stake. The Staking and delegation overview describes both as stake-rearrangement operations, but they act at different levels of the wallet model — one changes the delegation target, the other changes the owner.
Relationship to Coldkey
The coldkey is the ownership identity that transferring stake changes. The Glossary: Coldkey describes a coldkey as the security-critical key that controls TAO and stake, and transferring stake reassigns that control over a particular staked position to a new coldkey.
Relationship to Coldkey Swap
Transferring stake and coldkey swap both involve changing coldkey ownership of something on-chain, but they operate at different scopes. Transferring stake changes which coldkey owns a specific staked position — it reassigns ownership of one staked amount already placed with a validator while leaving other on-chain positions unchanged. Coldkey swap is a mechanism that moves an entire on-chain identity to a new coldkey, including all associated hotkeys and their subnet registrations, without resetting those registrations. The Staking and delegation overview describes transferring stake as a targeted ownership change for one staked position, and the Coldkey Swap documentation describes coldkey swap as moving on-chain identity to a new coldkey while preserving hotkey registrations.
A participant who wants a new coldkey to own one stake position while keeping everything else unchanged can use transferring stake. A participant who wants to move their entire on-chain identity — including all hotkeys, subnet registrations, and associated staking contexts — to a new coldkey would use coldkey swap instead. Transferring stake targets a single position; coldkey swap comprehensively reassigns the full on-chain identity that all those positions exist under.
References: Staking and delegation overview, Coldkey Swap
Relationship to Autostaking
Transferring stake and autostaking are related but distinct parts of Bittensor staking vocabulary. Transferring stake is the operation that changes which coldkey owns a particular staked position while keeping that stake on the same validator and subnet, while autostaking is a mechanism that automatically routes a miner’s emission proceeds into a staking position on a chosen validator. The Staking and delegation overview: Transferring stake describes transferring stake as a targeted ownership reassignment, and the Auto Staking for Miners documentation describes autostaking as automatically staking a miner’s emissions to a chosen validator.
For readers, transferring stake is a participant-side action that reassigns ownership of an existing staked position to a different coldkey, while autostaking is a continuous-routing mechanism that grows a validator’s stake from incoming emissions. The two are not interchangeable: transferring stake moves ownership of one staked position between coldkeys, autostaking automatically sends emission proceeds to a chosen validator. A miner who has accumulated a staked position through autostaking could later use transferring stake to move that position’s ownership to a different coldkey, but the two operations act on different sides of the staking flow.
References: Staking and delegation overview: Transferring stake, Auto Staking for Miners
Relationship to Conviction and Locked Stake
Transferring stake and conviction both act on an existing staked position, but they describe different things. Transferring stake is the operation of changing which coldkey owns a staked position, as the Staking and delegation overview describes. Conviction and locked stake, by the Conviction and locked stake documentation, describe locking subnet alpha so that it builds a time-based commitment score and the staked balance cannot be silently reduced below the locked amount.
For readers, transferring stake answers who owns a staked position, while conviction answers whether that position has been locked against reduction to signal commitment. The two are not interchangeable: transferring stake reassigns ownership of a position between coldkeys, whereas conviction is a lock that constrains how far the staked balance can be reduced. One changes the owner of a position; the other constrains reductions of the staked alpha and builds a commitment score over time.
References: Staking and delegation overview, Conviction and locked stake
Relationship to Yuma Consensus
Transferring 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, transferring 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 transferring stake as a concept. It does not describe transfer steps, recommend when to transfer, or state current stake amounts, fees, or subnet behavior. Readers should use the official staking documentation for operational detail.
Relationship to Coinbase
Transferring stake and coinbase are related but different parts of Bittensor’s stake management and emission pipeline. Transferring stake is a user-initiated operation that reassigns ownership of a staked position to a different coldkey. The Coinbase Implementation documentation describes coinbase as the per-block protocol mechanism that drives TAO emission, accumulates pending emissions, and triggers Yuma Consensus rounds at epoch boundaries, while the Staking and delegation overview describes the stake-management operations.
The two sit on different sides of the system. Transferring stake is a wallet-level action a participant chooses to perform on an existing staked position; coinbase is a protocol-level process the runtime executes every block to generate and advance emissions, not a user action. Transferring stake answers who controls a staked position and how it is reorganized across coldkeys or subnets; coinbase answers how the network produces emissions and triggers the epoch calculations that distribute them. One is a participant-facing stake-management operation, while the other is the recurring emission mechanism that operates regardless of any individual ownership change.
Development Stage Context
The Introduction to Bittensor describes subnet development as moving from localnet to testnet and then mainnet. For transferring stake, that sequence changes how readers should interpret evidence about stake transfer mechanics and ownership reassignment outcomes.
In localnet, stake transfer mechanics can be tested in an isolated environment. Localnet stake transfer outcomes reflect local chain configuration and do not represent production staking state.
On testnet, stake transfers can be observed in a shared, non-production network. Testnet stake transfer outcomes and coldkey assignment changes are separate from mainnet delegation state.
On mainnet, transferring stake is a live Subtensor action that reassigns ownership of delegated stake between coldkeys. The Staking and delegation overview describes the delegation mechanics that apply on the production network.
The Bittensor Networks reference separates mainnet, testnet, and localnet. A stake transfer example from one environment should not be read as representing ownership reassignment or staking outcomes in another environment.
Unstaking Withdraws; Transferring Stake Reassigns
The Staking and delegation overview lists direct unstaking and transferring stake as different ways to rearrange an existing delegated position. Unstaking withdraws stake back to the coldkey, often converting subnet alpha through the pool. Transferring stake instead changes which coldkey owns a position that remains delegated.
That distinction matters when the goal is custody change rather than exit. A participant who wants TAO back in the coldkey unstakes; a participant who wants the same delegated position under a new owner transfers instead of withdrawing and restaking separately (Glossary: Staking).
Moving Stake Changes the Validator Target Instead
Moving stake and transferring stake both rearrange an existing position, but they act on different wallet layers. Moving stake transfers delegated support between hotkeys and/or subnets in one atomic step, while transferring stake changes the owning coldkey without necessarily changing the validator hotkey that receives the delegation (Staking and delegation overview: Moving stake).
Readers comparing operations should match the change they need. Moving stake re-points delegation; transferring stake reassigns ownership of the same delegated position (Glossary: Hotkey).
The Delegated Position Stays Active After a Transfer
Transferring stake reassigns coldkey ownership while the stake itself stays in the delegated position described in official staking documentation. The validator relationship and subnet context can remain in place even though control moves to a different coldkey.
That is why transfer can be an alternative to unstaking and restaking from a new coldkey when only ownership needs to change. Operational steps, fees, and command details belong in official staking material rather than in this concept definition (Staking and delegation overview: Transferring stake).