Wallet Location
Wallet location is Bittensor wallet-file terminology for where generated Bittensor wallet files are stored on a user’s machine. The official Wallet Location glossary describes it as the directory path where generated Bittensor wallets are stored locally.
File-Storage Context
Wallet location is storage-location vocabulary, not a wallet role, address format, or key type. It describes where wallet files live on a local machine, while separate wallet and key terms describe the wallet material itself. Because that local directory can hold coldkey and hotkey file material, the location should be read as part of the workstation security boundary, not as a public account label (Wallets, Coldkeys and Hotkeys, Coldkey and Hotkey Workstation Security).
Wallet Context
Official wallet documentation is the surrounding context for Bittensor wallet concepts. In Taopedia prose, wallet location should be read as a file storage concept rather than an account-status claim or a security procedure.
Key Material Storage Context
The Glossary: Wallet Location identifies wallet location as where generated Bittensor wallets are stored on a local machine. Official wallet documentation treats that storage as holding local coldkey and hotkey file material. Wallet location therefore names a filesystem context for wallet keys, not an on-chain address or subnet participant role.
References: Glossary: Wallet Location, Bittensor wallet documentation
Wallet Location Names Local Storage, Not On-Chain Identity
Wallet location should not be read as a wallet address, subnet role, or proof of who controls keys on chain. It names the local directory path where generated Bittensor wallet files are stored (Glossary: Wallet Location, Bittensor wallet documentation).
Coldkey and hotkey material still supplies authority. The path only describes where those files live on a workstation (Wallets, Coldkeys and Hotkeys).
Path Labels Do Not Replace Key-Management Procedures
Wallet-location vocabulary does not provide recovery steps, backup policy, or signing instructions. Official key-management guidance covers creation, protection, and use of wallet material (Working with Keys, Handle your Seed Phrase/Mnemonic Securely).
Readers should keep procedural claims tied to those references rather than to directory-path labels alone.
Directory Paths Differ From Mnemonic Recovery
A filesystem path helps locate existing wallet files, while mnemonic vocabulary covers regeneration after loss. Path metadata is not recovery material (Glossary: Mnemonic, Glossary: Local Wallet).
Path and Authority Boundary
Wallet location points to where generated wallet files are stored; it does not itself grant wallet authority. The authority still comes from the coldkey and hotkey material described in the official wallet documentation, while the wallet-location glossary entry names the local path where those files are kept.
That boundary keeps a storage path from being read as a public address, account label, or separate wallet role. Moving or naming a directory changes the local file context, not the underlying cryptographic relationship between wallet keys and on-chain control.
Relationship to Wallets
Wallet location and wallets are related but different parts of Bittensor wallet vocabulary. A wallet is the cryptographic identity formed by coldkey and hotkey pairs used to access TAO and sign transactions, while wallet location describes the filesystem directory where the generated wallet files are stored locally on a user’s machine. The Bittensor wallet documentation describes wallets as the key-pair identity that proves control and accesses on-chain state, while the Glossary: Wallet Location describes wallet location as the local storage path for those generated wallet files.
For readers, the wallet names the cryptographic identity and on-chain control, while wallet location names where the local key files representing that identity are stored on disk.
References: Bittensor wallet documentation, Glossary: Wallet Location
Relationship to Coldkeys
Wallet location and coldkeys are related but different scopes in Bittensor wallet vocabulary. A coldkey is the security-sensitive cryptographic key that holds TAO balances and owns hotkeys, while wallet location describes the filesystem directory where generated coldkey files (and hotkey files) are stored on the local machine. The Wallets, Coldkeys and Hotkeys documentation treats coldkeys as the custody anchor that should be protected offline when possible, and the Glossary: Wallet Location describes wallet location as the local storage context for those wallet files.
For readers, the coldkey names the key material and on-chain identity, while wallet location names the local filesystem path where that key material is stored when generated on a machine.
References: Wallets, Coldkeys and Hotkeys, Glossary: Wallet Location
Relationship to Mnemonic
Wallet location and mnemonic are related through wallet recovery, but they describe different security surfaces. Wallet location names the local filesystem path where generated wallet files are stored, while a mnemonic is recovery material that can regenerate wallet keys if the local files are lost or deleted.
For readers, a wallet location can help identify where key files live on a machine, but it is not a backup phrase and cannot replace the recovery material. A mnemonic carries recovery authority, so it belongs in the sensitive seed-phrase handling context rather than ordinary file-location metadata.
References: Glossary: Wallet Location, Glossary: Mnemonic, Handle your Seed Phrase/Mnemonic Securely
Relationship to Yuma Consensus
Wallet Location 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, wallet location 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
Wallet location should not be read as a public address, a backup plan, or a command tutorial. It names where local wallet files are stored on a machine (Glossary: Wallet Location).
Wallet Files Reside in a Local Directory Path
The Glossary: Wallet Location describes wallet location as the directory path where generated Bittensor wallets are stored locally. Official wallet documentation treats that directory as holding coldkey and hotkey file material for local wallet use.
Readers should pair location vocabulary with workstation-security context. Knowing a path does not, by itself, describe who controls the keys inside the files.
Path Metadata Is Not Recovery Material
Wallet location differs from mnemonic recovery vocabulary. A filesystem path helps identify where local wallet files live, while seed-phrase guidance covers regeneration after loss (Glossary: Mnemonic, Glossary: Local Wallet).
Backup and recovery therefore belong to seed-phrase handling rather than to directory-path labels alone.
Development Stage Context
The Introduction to Bittensor describes subnet development as moving from localnet to testnet and then mainnet. For Wallet Location, this sequence gives readers a boundary for interpreting wallet-location examples and storage-environment notes.
Localnet examples are isolated and reflect local chain state, so they are useful for controlled experiments rather than evidence of live Bittensor behavior. Testnet examples add shared non-production conditions, which can reveal integration behavior without touching mainnet state.
On mainnet, Wallet Location examples should be read as live production wallet-location behavior on the production Bittensor network.
The Bittensor Networks reference separates mainnet, testnet, and localnet, so outcomes from one environment should not be treated as proof of behavior in another.