Wallet Address
A wallet address is the public-facing identifier used as a TAO destination in Bittensor. The official Wallet Address glossary describes it as a unique identifier derived from a public key and used for sending and receiving TAO tokens.
Address Context
A wallet address is address material, not private signing material. It identifies where TAO can be sent within Bittensor, while the protected key material that authorizes account activity is a separate wallet-key concept.
Signing Authority Boundary
A wallet address can be shared as a destination identifier, but it does not authorize movement from that address. Authorization belongs to protected private-key material, while public-key-derived address material supports account reference and receiving context (Glossary: Wallet Address, Glossary: Private Key).
Public-Key Context
The public-key relationship matters because the glossary defines wallet addresses as derived from public keys. The Public Key glossary describes public keys as shareable material used for verification, encryption, and account reference.
SS58 Address Format
Bittensor wallet addresses use SS58 encoding as the compact public-facing representation derived from a public key. The Glossary: SS58 Encoded describes SS58 as the encoding format for those addresses, while the Wallet Address glossary defines the address as the TAO destination identifier derived from that key material.
Wallet Context
Bittensor wallet documentation is the broader official context for wallet and key concepts. In Taopedia prose, a wallet address should be read as destination-address vocabulary rather than a wallet operation guide, balance claim, or live account-status claim (Bittensor wallet documentation).
Transfer Destinations Use Wallet Addresses
The official Glossary: Transfer describes transfer as sending TAO tokens between wallet addresses. A wallet address is therefore the destination identifier a sender targets when moving TAO on Subtensor.
Readers should read wallet address as the receiving-side label in transfer vocabulary. The transfer action names the movement; the wallet address names where the TAO is sent.
References: Glossary: Wallet Address, Glossary: Transfer
Sharing an Address to Receive TAO
A wallet address can be shared so someone else knows where to send TAO. The Glossary: Public Key describes public keys as shareable material used for account reference, and wallet addresses are derived from that public-side material for destination use.
Sharing an address is not the same as sharing signing authority. The Glossary: Private Key remains the protected material needed to authorize outbound actions from the account.
References: Glossary: Wallet Address, Glossary: Private Key
SS58 as the Native Display Format
Bittensor wallet addresses appear in SS58 encoded form as the compact public-facing representation derived from a public key. The Glossary: SS58 Encoded describes that encoding format for native Subtensor wallet destinations.
That format is separate from Ethereum-style H160 addresses used on the Bittensor EVM side. Wallet address in native Bittensor prose usually means the SS58 destination derived from a Subtensor public key, not an EVM account label.
References: Glossary: SS58 Encoded, Glossary: Wallet Address
Relationship to Address Poisoning Scams
Wallet addresses are the destination identifiers that address-poisoning scams target. The Glossary: Wallet Address describes a wallet address as a unique identifier derived from a public key and used for sending and receiving TAO tokens, and the Bittensor address-poisoning guide warns that similar-looking addresses can appear familiar during routine wallet use.
For readers, a wallet address names the destination identifier itself, while address poisoning names the risk that a lookalike identifier gets treated as the intended destination. The address stays cryptographically valid; the harm comes from mistaking one valid address for another.
References: Glossary: Wallet Address, Address Poisoning Scams guide
Relationship to Public Key
Wallet address and public key are related but different parts of Bittensor wallet-key vocabulary. A public key is shareable cryptographic key material used for verification and account reference, while a wallet address is the public-key-derived identifier used as a TAO destination. The Glossary: Public Key describes the public side of a keypair, and the Glossary: Wallet Address describes a wallet address as a unique identifier derived from a public key.
For readers, public key names the shareable keypair material, while wallet address names the destination identifier derived from that material.
References: Glossary: Public Key, Glossary: Wallet Address
Relationship to SS58 Encoded
Wallet address and SS58 encoded are related but different scopes in Bittensor address vocabulary. A wallet address is the TAO destination identifier derived from public-key material, while SS58 encoded names the compact representation format used for those addresses. The Glossary: Wallet Address describes the destination identifier, and the Glossary: SS58 Encoded describes SS58 as the encoding format for public-key-derived addresses.
For readers, wallet address names the destination concept, while SS58 encoded names the compact address format used to display it.
References: Glossary: Wallet Address, Glossary: SS58 Encoded
Relationship to TAO
Wallet address and TAO are related but different parts of Bittensor token vocabulary. TAO is the network incentive token, while a wallet address identifies where TAO can be sent within the network. The Glossary: TAO describes TAO as the token used to incentivize subnet activity, and the Glossary: Wallet Address describes a wallet address as used for sending and receiving TAO tokens.
For readers, TAO names the asset being moved, while wallet address names the destination identifier for that movement.
References: Glossary: TAO, Glossary: Wallet Address
Relationship to Transfer
Wallet address and transfer are related but different parts of Bittensor wallet vocabulary. A transfer names the act of sending TAO between wallet addresses, while a wallet address names the destination identifier used in that movement. The Glossary: Transfer describes transfer as sending TAO tokens between wallet addresses, and the Glossary: Wallet Address describes a wallet address as a TAO destination identifier.
For readers, transfer names the movement action, while wallet address names the destination identifier that action requires.
References: Glossary: Transfer, Glossary: Wallet Address
Relationship to Yuma Consensus
Wallet Address 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 address 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 address should not be read as a private key, a completed transfer, or proof that funds were received. It names the public destination identifier derived from key material and used when sending or receiving TAO (Glossary: Wallet Address).
Transfers Require an Exact Destination String
The Glossary: Transfer describes moving TAO between wallet addresses. Transfer vocabulary therefore depends on a precise destination identifier rather than on a similar-looking prefix alone (Address Poisoning Scams).
For readers, sharing or quoting an address is not the same as completing a transfer. Submission still requires the sender to specify the exact destination and authorize the move.
Public Address Material Is Not Signing Authority
Wallet documentation keeps public-side address material separate from protected private signing material. A wallet address can identify where TAO should be sent without exposing authorization to move funds from that account (Wallets, Coldkeys and Hotkeys, Glossary: Public Key).
Readers should not infer custody or spend authority from an address string alone.
Development Stage Context
The Introduction to Bittensor describes subnet development as moving from localnet to testnet and then mainnet. The wallet address concept applies across the Bittensor lifecycle: wallet addresses can be generated and used in localnet for isolated development, testnet for shared non-production participation, and mainnet for live operation with real emissions. Each network environment produces distinct address contexts.
The Bittensor Networks reference separates mainnet, testnet, and localnet. Wallet address examples or account-reference outcomes from one environment should not be read as representing production subnet participation in another environment.