Public Key

How a public key fits Bittensor wallet-key terminology as the shareable side of a cryptographic keypair.

A public key is the shareable side of a cryptographic keypair in Bittensor wallet-key terminology. The official Glossary: Public Key describes it as publicly available key material used for verifying signatures, encrypting messages, and identifying accounts in the Bittensor network.

Keypair Context

Public keys are read together with private keys. The public side can be shared for account reference or verification, while the Glossary: Private Key describes the private side as the protected component used to authorize transactions and operations.

This distinction keeps public key from being treated as a secret. It is still part of the same cryptographic keypair vocabulary, but it has a different role from private signing material.

Wallet-Key Context

In Bittensor, public keys belong to wallet-key terminology rather than naming a separate network role or token. The Glossary: EdDSA Cryptographic Keypairs connects public and private key pairs with coldkeys and hotkeys, which are Bittensor wallet-key roles.

For readers, the useful point is structural: a public key is part of the wallet-key system used to identify and verify, not a staking position, subnet role, or balance.

Signature Verification Role

The official Glossary: Public Key describes public key material as used for verifying signatures on Bittensor network activity. That verification role is separate from private-key authorization: the public side confirms which key pair an account reference belongs to, while the private side actually signs submissions.

In Bittensor, a public key is used for verification and identification; it is not a recovery secret and does not authorize signing. The matching private key is the protected signing material (Glossary: Public Key, Glossary: Private Key).

References: Glossary: Public Key, Glossary: Private Key

EdDSA Keypair Format

Bittensor wallet keys are discussed through EdDSA cryptographic keypairs in official glossary wording. The Glossary: EdDSA Cryptographic Keypairs connects those pairs to coldkeys and hotkeys, which are the operational wallet roles participants use for funds control and subnet actions.

For readers, public key names the shareable half of that pair format. Coldkey and hotkey names are role labels built on top of the underlying keypair vocabulary rather than replacements for it.

References: Glossary: EdDSA Cryptographic Keypairs, Glossary: Public Key

Identification Without Authorization

Public key material can identify an account reference, but it does not by itself authorize transfers, staking actions, or subnet registrations. The Glossary: Private Key describes the protected component used to authorize transactions and operations on the network.

That split helps readers keep shareable reference material separate from protected signing material when reading wallet-security documentation alongside key vocabulary.

References: Glossary: Public Key, Glossary: Private Key

Relationship to Wallet Addresses

Wallet addresses are related but not identical. The Glossary: Wallet Address describes a wallet address as a public-key-derived identifier used as a TAO destination. The Glossary: SS58 Encoded describes SS58 encoded values as compact representations of those public-key-derived addresses.

This means public key is the cryptographic keypair concept, while wallet address and SS58 encoded describe address representation and destination context.

Relationship to Address Poisoning Scams

Public keys are the keypair material that wallet addresses are derived from, which is why two different addresses can share display characteristics. The Glossary: Public Key describes a public key as shareable material used for account reference, and the Bittensor address-poisoning guide warns that similar-looking addresses can appear familiar during routine wallet use.

For readers, a public key names the shareable keypair material, while address poisoning names the risk that a lookalike derived address gets treated as the intended destination. Each public key produces its own address, but those addresses can still look similar enough in abbreviated form to mislead a user.

References: Glossary: Public Key, Address Poisoning Scams guide

Relationship to Yuma Consensus

Public Key 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, public key 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

Public key should not be read as a recovery phrase, a private key, or a complete wallet by itself. It is a shareable public component used in identification and verification context. This article does not describe how to create, store, recover, rotate, or use wallet keys.

Relationship to Private Key

Public key and private key are related but different sides of Bittensor cryptographic keypair vocabulary. A public key is shareable material used for verification and account reference, while a private key is the protected component used to authorize transactions and operations. The Glossary: Public Key describes the public side of the pair, and the Glossary: Private Key describes the private side as protected authorization material.

For readers, public key names the shareable pair side, while private key names the protected side that must remain secret because it authorizes activity.

References: Glossary: Public Key, Glossary: Private Key

Relationship to Coldkeys

Public key and coldkey are related but different scopes in Bittensor wallet-key vocabulary. Public key names the shareable side of a cryptographic keypair, while coldkey names the security-sensitive wallet key that controls TAO and stake. The Glossary: Public Key describes public key as shareable key material, and the Glossary: Coldkey describes the coldkey as the key that controls TAO and stake.

For readers, public key names the keypair reference concept, while coldkey names the specific wallet role that uses protected key material to control funds and stake.

References: Glossary: Public Key, Glossary: Coldkey

Relationship to Hotkeys

Public key and hotkey are related but different scopes in Bittensor wallet-key vocabulary. Public key names the shareable side of a cryptographic keypair, while hotkey names the operational wallet key used for routine on-chain actions such as registration and weight submission. The Glossary: Public Key describes public key as shareable key material, and the Glossary: Hotkey describes the hotkey as the operational key used by miners, validators, and subnet actors.

For readers, public key names the shareable reference concept, while hotkey names the operational wallet role derived under coldkey control for subnet actions.

References: Glossary: Public Key, Glossary: Hotkey

Relationship to Extrinsics

Public key and extrinsics are related but different parts of Bittensor chain action vocabulary. Extrinsics name signed transactions and calls submitted to Subtensor, while public key names the shareable key material used to identify accounts referenced in those submissions. The Glossary: Extrinsics describes signed transactions submitted to the chain, and the Glossary: Public Key describes public key as shareable material used for verifying signatures and identifying accounts.

For readers, extrinsics name submitted chain actions, while public key names the shareable account reference material associated with those actions.

References: Glossary: Extrinsics, Glossary: Public Key

Development Stage Context

The Introduction to Bittensor describes subnet development as moving from localnet to testnet and then mainnet. The public key concept applies across the Bittensor lifecycle: key pairs can be generated and used for account identification in localnet for isolated development, testnet for shared non-production participation, and mainnet for live operation with real emissions.

The Bittensor Networks reference separates mainnet, testnet, and localnet. Public key examples or account reference outcomes from one environment should not be read as representing production subnet participation in another environment.

Further Reading

Topics WalletsSecurity
Last updated (UTC) 7 min read