External Wallet
An external wallet is wallet software or custody outside the local Bittensor wallet path. The External Wallet glossary entry places the term in wallet-security vocabulary, where location and custody context matter for how a wallet is understood.
Custody Context
External wallet names a custody context, not a different token or subnet role. The wallet documentation gives the broader setting for Bittensor wallet concepts, while the external-wallet glossary entry narrows the term to wallet software or custody outside the local path.
Wallet Application Boundary
External wallet and wallet application are related but not interchangeable. The external-wallet glossary entry points to custody or software outside the local wallet path, while wallet-application vocabulary describes the software interface used to view wallet state or prepare actions (Wallet application, Wallets).
For readers, an external wallet answers where custody or signing control is managed. A wallet application answers which interface is being used to interact with wallet information or actions.
Local Wallet Contrast
The contrast term is local wallet. A local wallet belongs to the local Bittensor wallet path, while an external wallet places that wallet context outside the local path. The difference is about where wallet control is managed, not about creating a separate Bittensor asset.
Wallet Address Boundary
External wallet and wallet address are related but separate concepts. A wallet address is a public-key-derived destination identifier for TAO, while external wallet names custody or software context. That distinction keeps destination-address vocabulary separate from custody-location vocabulary.
Address-Poisoning Context
External wallets still use destination addresses, so address-poisoning risk remains relevant. The address-poisoning guide focuses on lookalike destination addresses during wallet use, while the external-wallet term names where wallet control is managed. The risk and the custody context are connected but not identical.
Relationship to Public and Private Keys
External wallet sits near key vocabulary because wallets organize access around key material. A public key is shareable reference material, while a private key is protected authorization material. External wallet does not rename either side of that pair.
Relationship to Ledger Hardware Wallet
External wallet and Ledger hardware wallet are related but different wallet-security ideas. An external wallet names custody or wallet software outside the local Bittensor wallet path, while a Ledger hardware wallet names a hardware signing device used with compatible wallet applications.
For readers, external wallet answers where wallet control is managed. Ledger hardware wallet answers how protected signing material can stay on a dedicated device during supported wallet-app operations.
References: Glossary: External Wallet, Using Ledger Hardware Wallet
Reader Boundary
External wallet should not be read as a subnet role, validator recommendation, wallet provider endorsement, or balance state. It names custody-location vocabulary for wallet software or signing control outside the local Bittensor wallet path (Glossary: External Wallet, Wallets).
For readers, external wallet answers where custody or signing control is managed. Wallet address, public key, and private key vocabulary describe destination and key material rather than custody location (Glossary: Wallet Address, Glossary: Private Key).
External Wallet Does Not Change Destination Format
An external wallet can still sign transfers to the same SS58 destination format used elsewhere in Bittensor wallet prose. Custody location and destination address are separate questions (Glossary: Wallet Address, Address Poisoning Scams).
That keeps address-poisoning guidance relevant without treating wallet software choice as proof about subnet behavior or validator selection.
Signing Control Stays Separate From Subnet Roles
External wallet vocabulary belongs with wallet security and signing context. Miner, validator, and nominator roles describe network participation rather than where keys are stored (Staking and delegation overview, Wallets, Coldkeys and Hotkeys).
Using the right boundary prevents wallet-interface examples from being read as role claims on a subnet.
Development Stage Context
The Introduction to Bittensor describes subnet development as moving from localnet to testnet and then mainnet. For External Wallet, this sequence gives readers a boundary for interpreting wallet-connection examples and network-selection 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, External Wallet examples should be read as live production wallet 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.
Custody Interface Scope
An external wallet should be read as a custody or signing interface around keys, not as a Bittensor protocol role like miner, validator, or nominator. Wallet documentation explains account material, while staking documentation explains role-specific network participation (Wallets, Coldkeys and Hotkeys, Staking and delegation overview).
The external-wallet boundary is about where signing control and key material are managed. It does not change the wallet address vocabulary, TAO destination format, or subnet role being discussed. Keeping those contexts separate avoids treating wallet software choice as evidence about subnet behavior or validator selection.