EdDSA Cryptographic Keypairs
EdDSA cryptographic keypairs are Bittensor wallet-key vocabulary for public and private key pairs generated with EdDSA. The EdDSA Cryptographic Keypairs glossary entry places the term in the keypair layer behind Bittensor key roles.
Algorithm Context
EdDSA names the signature algorithm context, while a keypair names the paired public and private material produced under that context. In the EdDSA glossary entry, the term is used for the cryptographic method behind Bittensor public/private keypair terminology.
Public and Private Sides
A keypair has a public side and a private side. The Public Key glossary entry places public keys in shareable verification and account-reference context, while the Private Key glossary entry places private keys in authorization context. EdDSA keypairs supply that paired structure.
Wallet-Key Vocabulary
In Bittensor, EdDSA keypairs belong to wallet-key terminology rather than subnet, consensus, or tokenomics terminology. The wallet documentation provides the broader setting for Bittensor wallet concepts, while the EdDSA glossary entry narrows the subject to the cryptographic keypair layer.
Coldkey and Hotkey Roles Use Keypairs
The official Glossary: EdDSA Cryptographic Keypairs connects EdDSA keypairs to coldkeys and hotkeys in Bittensor wallet vocabulary. Those role labels describe how generated key material is used on the network, while EdDSA names the cryptographic method behind the paired public and private keys.
Readers should keep algorithm vocabulary separate from role vocabulary. EdDSA keypairs explain the pair structure; coldkey and hotkey explain which wallet role uses that material for custody or routine subnet actions.
References: Glossary: EdDSA Cryptographic Keypairs, Glossary: Coldkey
Signature Algorithm, Not a Wallet Operation
EdDSA names the signature algorithm context for Bittensor public and private key pairs. It does not name a transfer, staking action, registration step, or subnet role by itself. The Glossary: Public Key and Glossary: Private Key entries describe what each side of the pair is used for after the keypair exists.
For readers, EdDSA belongs in wallet-security reading when documentation discusses how Bittensor key material is generated and signed, not when it discusses emissions, validator weights, or subnet tasks.
References: Glossary: EdDSA Cryptographic Keypairs, Glossary: Private Key
Shareable Public Side Versus Protected Private Side
One side of an EdDSA keypair is public shareable material used for account reference and signature verification. The other side is private authorization material that must stay protected. The glossary entries for public key and private key supply that split, while EdDSA keypairs name the paired structure both sides come from.
That split helps readers avoid treating a public key like signing authority, or a private key like a destination address. The keypair vocabulary names both sides together; public-key and private-key vocabulary names what each side does in wallet use.
Wallet documentation remains the place for operational key-handling detail; EdDSA keypairs name the cryptographic pair structure those roles build on.
References: Glossary: Public Key, Glossary: Private Key
Relationship to Public Keys
Public keys are one side of the keypair. They are the shareable material used for account reference and verification, not the protected signing side. The Public Key glossary entry supplies that boundary, and EdDSA keypairs explain where the public side comes from.
Relationship to Private Keys
Private keys are the protected side of the keypair. They are related to EdDSA keypairs because the pair includes private signing material, but the term EdDSA names the cryptographic keypair context rather than instructions for using that material. The Private Key glossary entry gives the private-side meaning.
EdDSA Keypairs Name Signing Material, Not Balances
EdDSA cryptographic keypairs should not be read as TAO balances, subnet roles, or wallet application labels. The term names the cryptographic pair structure behind Bittensor signing material (Glossary: EdDSA Cryptographic Keypairs, Bittensor wallet documentation).
Coldkey and hotkey vocabulary describes how generated key material is used after the pair exists. EdDSA names the algorithm context for that paired generation step.
Algorithm Labels Do Not Replace Key-Management Procedures
EdDSA keypair vocabulary does not provide wallet creation 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 algorithm labels alone.
Mnemonic Material Differs From the Keypair Label
Mnemonic vocabulary covers regeneration after loss, while EdDSA keypairs name the cryptographic pair structure produced during wallet generation. Recovery phrases are not the same label as the algorithm context (Glossary: Mnemonic, Glossary: EdDSA Cryptographic Keypairs).
Development Stage Context
The Introduction to Bittensor describes subnet development as moving from localnet to testnet and then mainnet. For EdDSA Cryptographic Keypairs, this sequence gives readers a boundary for interpreting keypair examples and signing-context 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, EdDSA Cryptographic Keypairs examples should be read as live production signing 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.
Relationship to Yuma Consensus
EdDSA Cryptographic Keypairs 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, eddsa cryptographic keypairs 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
EdDSA cryptographic keypairs should not be read as wallet applications, recovery phrases, subnet roles, or TAO balances. The term names the cryptographic keypair context behind Bittensor signing material (Glossary: EdDSA Cryptographic Keypairs).
Wallet Creation Generates a Fresh Key Pair
Working with Keys describes wallet creation as generating cryptographic key material for coldkeys and hotkeys. EdDSA keypair vocabulary sits at that generation layer rather than at subnet participation or balance labels (Wallets, Coldkeys and Hotkeys, Glossary: EdDSA Cryptographic Keypairs).
For readers, keypair generation is upstream of wallet roles. Coldkey and hotkey labels describe how generated pairs are used inside wallet structure.
SS58 Addresses Display Public Key Destinations
The Glossary: SS58 Encoded describes the compact format used for public-key-derived addresses, while the Glossary: Wallet Address describes the destination identifier used for TAO movement. Those terms belong to the public side of wallet vocabulary rather than to the protected private pair (Glossary: Public Key).
A precise claim should keep address-display vocabulary separate from private signing material.
Key Pair Scope
EdDSA cryptographic keypairs should be read as the cryptographic key material that backs a Bittensor wallet account, not as a separate account type or balance unit. Wallet and working-with-keys references explain how the keypair relates to coldkey and hotkey structure, while the glossary entry anchors the term itself (Bittensor Wallets, Glossary: EdDSA Cryptographic Keypairs).
For readers, a precise claim should keep the keypair vocabulary distinct from account, subnet, or TAO-balance language. The keypair names the signing material, while wallet structure and subnet participation name the higher-level context that uses that material.