Stake
Stake is the amount of currency tokens associated with a validator position in a Bittensor subnet (Glossary: Stake, Staking and delegation overview). It is amount vocabulary, not the action vocabulary of staking and not the downstream weighting vocabulary of stake weight.
The term should stay attached to its validator and subnet context. A stake amount by itself is not a wallet balance, validator ranking, or network-wide performance signal.
Validator Position Amount
Stake is read in relation to validator support. A TAO holder can stake to a validator, and a validator’s total stake can include both the validator’s own stake and stake delegated by others (Glossary: Delegation, Glossary: Nominator).
That combined view matters when reading Bittensor consensus and emission material. Stake names the support amount associated with the validator position; it does not say who supplied every portion unless the surrounding context identifies self-stake or delegated support.
This makes stake broader than delegate stake but narrower than every economic fact about an account. Delegate stake identifies the validator’s own supplied portion, while nominated or delegated support can add to the validator-associated stake context (Glossary: Delegate Stake, Glossary: Delegation).
The amount should therefore be read with the relationship attached. If the question is who supplied the support, nominator and delegate-stake vocabulary are more precise. If the question is the validator-associated amount, stake is the broader term.
Custody Boundary
Stake describes token support attached to a validator relationship, not a separate key-custody system. Wallet documentation explains where coldkey and hotkey material is managed, while staking documentation explains how token support is attached to validators (Wallets, Coldkeys and Hotkeys, Staking and delegation overview).
That boundary keeps stake from being mistaken for spending authority. A statement that tokens are staked identifies their validator-support context; it does not by itself identify where the wallet keys are stored or who can sign unrelated wallet actions.
Subnet Context
Stake is local to subnet state. Staking into subnets places stake in that subnet’s alpha-token context, and subnet references use validator stake weight when explaining validator influence inside a subnet (Staking into Subnets, Glossary: Alpha Tokens, Understanding Subnets: Validator stake weight).
This locality keeps stake from becoming one universal account number. A precise statement about stake should identify the subnet, validator, and asset context being discussed.
The asset context matters because subnet staking can be discussed through alpha-token vocabulary while Root-side staking is discussed through TAO staked through Root. A static article should not collapse those contexts into one undifferentiated amount (Glossary: Alpha Tokens, Glossary: Root Subnet).
For source reading, the relevant question is which staking path is being discussed. A subnet-local stake statement, a Root Subnet staking statement, and a wallet-balance statement are related but not interchangeable.
Stake Weight and Delegation
Stake and stake weight are related but not identical. Stake names the validator-associated amount, while stake weight is the interpreted measure used for validator consensus power and emissions (Glossary: Stake Weight, Understanding Subnets: Validator stake weight).
Delegation is the process that can attach holder support to a validator. Stake is the resulting amount that can include both self-supplied and delegated support (Glossary: Delegation, Glossary: Stake).
Effective stake is another nearby amount term. It summarizes total staked TAO associated with a delegate after the delegate’s own stake and nominator-delegated stake are counted (Glossary: Effective Stake, Glossary: Stake).
Those distinctions keep a useful order: delegation describes how support is attached, stake describes the validator-associated amount, effective stake summarizes the delegate-associated total, and stake weight describes the consensus-power interpretation.
Development Stage Context
The Introduction to Bittensor describes subnet development as moving from localnet to testnet and then mainnet. Stake examples from one environment should not be treated as evidence for another because validator sets, balances, and subnet staking state are environment-specific (Bittensor Networks).
Localnet examples can test staking mechanics in isolation. Testnet examples add shared non-production staking state. Mainnet stake interpretation concerns production validator relationships on the active network.
Reader Boundary
Stake is amount vocabulary for validator-associated support. It is not wallet custody, a validator ranking, or stake weight itself (Glossary: Stake, Glossary: Stake Weight).
A stake amount should stay attached to its validator and subnet context.
Relationship to Staking
Stake and staking are related but different parts of Bittensor validator-support vocabulary. Staking names the process of attaching TAO support to a validator, while stake names the amount associated with that supported validator position after support is attached (Glossary: Staking, Glossary: Stake).
For readers, staking is the action vocabulary and stake is the resulting amount vocabulary. A TAO holder performs staking to support a validator; the validator’s stake is the measured token amount that includes both own and delegated support. The terms belong to the same domain but name process versus amount.
References: Glossary: Stake, Glossary: Staking
Further Reading
- Glossary: Stake
- Glossary: Validator
- Glossary: Stake Weight
- Glossary: Delegation
- Glossary: Delegate Stake
- Glossary: Effective Stake
- Glossary: Root Subnet/Subnet Zero
- Wallets, Coldkeys and Hotkeys
- Staking and delegation overview
- Staking into Subnets
- Bittensor Networks
- Understanding Subnets: Validator stake weight