Private Key
A private key is the protected side of a cryptographic key pair in Bittensor wallet terminology. The Private Key glossary entry places it in authorization context, paired with public key material that can be referenced more openly.
Protected Pair Side
Private key names one side of a pair. The EdDSA Cryptographic Keypairs glossary entry places Bittensor public and private key pairs under EdDSA terminology, while the private-key entry narrows the focus to the protected authorization side of that pair.
Public-Key Contrast
The contrast with public keys is central. A public key is shareable material used for verification, encryption, and account reference. A private key is different because it is associated with authorization, so the two terms should not be treated as interchangeable wallet labels.
Authorization Context
Private keys matter because authorization and account reference are separate ideas. Public material can identify or verify, while the private side is the authorization component in the keypair. The Private Key glossary entry keeps that authorization boundary explicit.
Wallet-Key Vocabulary
In Bittensor, private key belongs to wallet-key vocabulary rather than subnet or consensus vocabulary. The wallet documentation provides the broader wallet context, while the private-key glossary entry anchors the narrower protected-key meaning.
Each Wallet Role Holds Its Own Private Key
Official Wallets, Coldkeys and Hotkeys in Bittensor documentation states that each coldkey and each hotkey is a cryptographic key pair with its own private and public material. A Bittensor wallet therefore contains more than one protected private side when it includes both a coldkey and one or more hotkeys.
The Glossary: EdDSA Cryptographic Keypairs places those pairs under EdDSA terminology for both coldkeys and hotkeys. Private key names the protected side inside each pair, while coldkey and hotkey name which wallet role that particular pair serves. One coldkey private key and one hotkey private key are separate secrets, not two labels for the same authorization material.
That structure also explains why a wallet can hold multiple hotkeys under one coldkey. Each added hotkey brings its own key pair and therefore its own private key, even though all of those hotkeys remain tied to the same owning coldkey in wallet vocabulary.
References: Wallets, Coldkeys and Hotkeys in Bittensor, Glossary: EdDSA Cryptographic Keypairs
The Public Side Derives From the Private Side
Official Wallets, Coldkeys and Hotkeys in Bittensor documentation states that the public key in each pair is mathematically derived from the private key. The private key remains the closely held secret, while the derived public material can be shared for verification and account reference.
The Glossary: Public Key describes that shareable side as used for verifying signatures, encrypting messages, and identifying accounts. Private key vocabulary therefore names the root secret inside the pair, and public key vocabulary names the derived material others can reference without receiving signing authority.
That derivation direction matters when reading wallet-security material. Losing or exposing a private key compromises the whole pair because the public side is computed from it, not stored as an independent secret you can rotate separately from the protected side.
References: Wallets, Coldkeys and Hotkeys in Bittensor, Glossary: Public Key
Coldkey and Hotkey Private Keys Sign Different Work
Official Wallets, Coldkeys and Hotkeys in Bittensor documentation assigns different authorization work to the two private keys inside a wallet. The coldkey private key is needed for transferring TAO balances, managing stake, subnet management and governance actions, and managing hotkeys. The hotkey private key is needed for miners to serve requests in subnets and for validators to send requests to miners and submit weights to the chain.
The Glossary: Hotkey describes the hotkey as the operational wallet component used for routine network actions such as registration and weight submission, while Glossary: Coldkey vocabulary stays with fund custody and high-risk financial operations. Private key is the shared pair-side term; which private key must sign depends on whether the action belongs to coldkey-side custody or hotkey-side subnet operation.
Keeping that split explicit prevents reading every signed submission as coldkey fund authority. Subnet participation can require the hotkey private key even when no TAO transfer or stake movement is involved, because the documented hotkey-side list covers miner service and validator weight submission rather than balance custody.
References: Wallets, Coldkeys and Hotkeys in Bittensor, Glossary: Hotkey
Relationship to Seed Phrases
Private keys and seed phrases sit on the same protected side of wallet security, but they name different things. A private key is the authorization material inside a keypair, while a seed phrase or mnemonic is recovery material that can regenerate wallet key material. That means seed-phrase handling should be read as protection for the private-key authority behind the wallet, not as a public account-labeling detail.
The Working with Keys guide describes wallet creation as generating a unique mnemonic for each key, so a given seed phrase recovers one specific key pair rather than every key in a wallet.
References: Glossary: Private Key, Handle your Seed Phrase/Mnemonic Securely, Working with Keys
Relationship to Wallet Addresses
Wallet addresses and private keys are related but not the same. A wallet address is a public-key-derived destination identifier, while a private key is protected authorization material. This keeps destination-address vocabulary separate from keypair authorization vocabulary.
Private Key Names Authorization Material, Not an Address
Private key should not be read as a wallet address, a mnemonic, or a public account profile. The term names the protected authorization side of a cryptographic key pair (Glossary: Private Key, Glossary: Wallet Address).
Wallet addresses identify destinations derived from public key material; private keys authorize signed actions from the protected pair side.
Key-Management Guidance Covers Procedures
Private key vocabulary does not provide wallet creation steps, backup policy, or signing instructions. Official key-management guidance covers generation, 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 private-key labels alone.
Public Labels Differ From Signing Authority
The Glossary: Public Key describes shareable verification and account-reference material, while private key names the protected signing side. That split keeps destination-address vocabulary separate from authorization vocabulary (Bittensor wallet documentation).
Recovery Phrase Boundary
Private key and mnemonic are related but different wallet-security terms. A private key is the protected authorization side of a key pair, while a mnemonic is recovery material that can recreate wallet keys after loss (Glossary: Private Key, Glossary: Mnemonic).
For readers, that keeps daily signing authority separate from recovery custody. The mnemonic should be protected because it can restore access, but it should not be treated as the public address, wallet application, or ordinary label for the account (Bittensor wallet documentation).
Reader Boundary
Private key should not be read as a wallet address, a mnemonic, a subnet role, or a balance label. It names the protected authorization side of a cryptographic key pair (Glossary: Private Key).
Regenerating a Key Restores One Pair at a Time
The Glossary: Regenerating a Key describes recovering wallet key material from recovery information for a specific key. That path rebuilds access to one coldkey or hotkey pair rather than every key in a wallet automatically (Working with Keys, Wallets, Coldkeys and Hotkeys).
For readers, recovery vocabulary and private-key vocabulary answer different questions. Recovery material can restore a key; private key names the protected signing side once the pair exists.
Seed-Phrase Guidance Covers Recovery Custody
Handle your Seed Phrase/Mnemonic Securely frames recovery phrases around loss and disclosure risk. That guidance belongs to recovery custody rather than to everyday public-side account reference (Glossary: Mnemonic, Glossary: Private Key).
Keeping those layers separate helps readers avoid treating a mnemonic like a routine wallet label or treating a public address like protected signing material.
Development Stage Context
The Introduction to Bittensor describes subnet development as moving from localnet to testnet and then mainnet. The private key concept applies across the Bittensor lifecycle: key pairs can be generated and used in localnet for isolated development, testnet for shared non-production participation, and mainnet for live operation with real emissions. Private keys controlling mainnet wallets require the strongest protection because they authorize real TAO operations.
The Bittensor Networks reference separates mainnet, testnet, and localnet. A private key’s security requirements depend on which network the associated wallet operates on.