SS58 Encoded
SS58 encoded values are compact representations used for Bittensor wallet addresses. The SS58 Encoded glossary places the term in wallet-address context, where public-key-derived address strings identify TAO destinations.
Address Representation
An SS58 encoded value is not a separate asset or account role. It is an address representation. The Wallet Address glossary describes wallet addresses as public-key-derived identifiers used as TAO destinations in the Bittensor network.
Public-Key Context
The public-key side of the term matters because SS58 encoded values represent public-key-derived addresses. A public key is shareable material used for verification, encryption, and account reference in Bittensor; private signing material is outside the SS58 encoded address-format concept.
Wallet Context
In reader-facing Taopedia prose, SS58 encoded should be read as address-format vocabulary. It connects the compact representation described in the SS58 Encoded glossary with the destination-address meaning described for wallet addresses.
SS58 Is the Native Address Format
SS58 encoded values are the compact strings used to display public-key-derived Bittensor wallet addresses on the Substrate side of the network (Glossary: SS58 Encoded, Glossary: Wallet Address).
Readers use those strings as TAO destination labels in transfer and staking prose.
An Address String Is Not a Balance or Role
An SS58 encoded value identifies where TAO can be sent. It does not by itself show a balance, a staking position, or proof that the holder controls the corresponding key material (Glossary: SS58 Encoded, Glossary: Public Key).
Chain state and wallet-key documentation answer those separate questions.
Wallet Documentation Covers Conversion Steps
Conversion between SS58 and H160 address views is documented in the official EVM tutorials rather than in this concept article (Convert Ethereum H160 Address to Substrate SS58, Token Bridging).
Readers should use those guides when an operation requires a different address format.
Related articles
Substrate-Side Address Format
SS58 encoding names the compact display format for public-key-derived addresses on the Substrate side of Bittensor wallet activity. The glossary places SS58 encoded values in wallet-address context where those strings identify TAO destinations for transfers and other Substrate-side operations on the Bittensor chain.
Readers should treat SS58 as a representation layer, not a second asset or account type. The same wallet identity can be discussed through public-key material and through its SS58-encoded address string; the encoding changes how the address is shown and parsed, not what on-chain identity it refers to. Conversion tooling, checksum behavior, and address checks belong in official wallet documentation rather than in a static article quote.
References: Glossary: SS58 Encoded, Glossary: Wallet Address
Distinct From H160 EVM Addresses
Bittensor also uses H160-style addresses in EVM contexts through token bridging and EVM tutorials. SS58 encoded values belong to Substrate wallet addressing, while H160 addresses belong to the EVM account format described in bridging documentation. The two formats serve different execution paths on the same chain rather than interchangeable labels for one interface.
Readers evaluating transfers or contract use should confirm which account format an operation expects. Bridging moves TAO between SS58 and H160 contexts; SS58 encoded naming stays on the Substrate-side destination format rather than on EVM wallet labels. The H160 address article describes the EVM-side format separately from SS58 display strings. Live tooling determines which format a given action requires at submission time. Address conversion tutorials carry the operational detail for moving between formats rather than this concept article.
References: Glossary: SS58 Encoded, Token Bridging
Address Display Versus Private Signing Material
An SS58 encoded string is derived from public-key material and is intended for sharing as a destination address. Private keys, mnemonics, and other signing or recovery material remain outside the SS58 concept. The public-key glossary describes shareable verification material; SS58 encoded names how that material is represented as a compact address string for readers and tools.
That boundary matters when reading wallet documentation. Publishing an SS58 address for receiving TAO is normal; publishing recovery phrases or private keys is not. SS58 encoded vocabulary helps readers talk about destination addresses without conflating them with custody secrets described in seed phrase and workstation security documentation. Destination addresses and custody secrets should stay in separate handling categories when reading wallet safety material.
References: Glossary: SS58 Encoded, Glossary: Public Key
Relationship to Wallet Address
SS58 encoded and wallet address are related but different scopes in Bittensor address vocabulary. A wallet address is the public-key-derived identifier used as a TAO destination, while SS58 encoded names the compact representation format used for those addresses. The Glossary: Wallet Address describes a wallet address as a unique identifier derived from a public key, 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 Public Key
SS58 encoded 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 SS58 encoded names the compact address representation derived from that material. The Glossary: Public Key describes the public side of a keypair, and the Glossary: SS58 Encoded describes SS58 as the encoding format for public-key-derived addresses.
For readers, public key names the shareable keypair material, while SS58 encoded names the address format derived from it.
References: Glossary: Public Key, Glossary: SS58 Encoded
Relationship to TAO
SS58 encoded and TAO are related but different parts of Bittensor token vocabulary. TAO is the network incentive token, while SS58 encoded names the compact address format used to identify TAO destinations. The Glossary: TAO describes TAO as the token used to incentivize subnet activity, and the Glossary: SS58 Encoded describes SS58 as the encoding format for public-key-derived wallet addresses used as TAO destinations.
For readers, TAO names the asset being sent, while SS58 encoded names the address format that identifies where that asset can be sent.
References: Glossary: TAO, Glossary: SS58 Encoded
Relationship to Transfer
SS58 encoded and transfer are related but different parts of Bittensor wallet vocabulary. Transfer names the act of sending TAO between wallet addresses, while SS58 encoded names the compact address format used to identify those destinations. The Glossary: Transfer describes transfer as sending TAO tokens between wallet addresses, and the Glossary: SS58 Encoded describes SS58 as the encoding format for those public-key-derived addresses.
For readers, transfer names the movement action, while SS58 encoded names the address format used to identify the endpoints of that movement.
References: Glossary: Transfer, Glossary: SS58 Encoded
Relationship to Coldkey Swap
SS58 encoded and coldkey swap are related but different parts of Bittensor wallet vocabulary. An SS58 encoded value is the compact, public-key-derived address format used to identify wallets on the Bittensor network — the address format that identifies where TAO is held and where on-chain actions originate. Coldkey swap is the on-chain identity migration that moves all hotkeys associated with a coldkey to a new coldkey address without resetting their subnet registrations or removing existing stake. The Glossary: SS58 Encoded describes the address encoding format, and the Coldkey Swap documentation describes how an identity can be migrated to a new coldkey while preserving existing hotkey state.
A coldkey swap changes which SS58 address controls a set of hotkeys. Before the swap, the original coldkey’s SS58 address is the controlling identity; after the swap, the new coldkey’s SS58 address becomes the controlling identity, inheriting the same hotkeys and their registrations. SS58 encoded names the address format that identifies a coldkey at any point; coldkey swap names the migration event that changes which SS58 address holds that control.
References: Glossary: SS58 Encoded, Coldkey Swap
Reader Boundary
SS58 encoded should be read as native wallet address-format vocabulary. It identifies public-key-derived destinations on Bittensor; it does not by itself prove signing authority or subnet role status (Glossary: SS58 Encoded).
SS58 Identifies Native Bittensor Destinations
The Glossary: SS58 Encoded describes SS58 as the encoding format for public-key-derived Bittensor wallet addresses. Transfer and staking prose therefore use SS58 strings to name where native Subtensor actions are aimed (Glossary: Wallet Address).
Readers should treat SS58 as the native address view for Bittensor wallets, separate from Ethereum-style H160 account labels used in the EVM layer (Bittensor EVM Smart Contracts).
H160 Conversion Changes View, Not Control
Official conversion documentation explains that users can translate between H160 and SS58 representations for transfers or account views, but conversion does not produce the corresponding private key (Convert Ethereum H160 Address to Substrate SS58).
SS58 and H160 therefore name related address views across wallet contexts. Signing authority still follows the private key for the environment where the action is performed.
Development Stage Context
The Introduction to Bittensor describes subnet development as moving from localnet to testnet and then mainnet. The SS58 encoded concept applies across the Bittensor lifecycle: public-key-derived address strings are used in localnet for isolated chain testing, on testnet for shared non-production wallet operations, and on mainnet for live operation with real TAO destinations.
The Bittensor Networks reference separates mainnet, testnet, and localnet. SS58 address examples or wallet-destination outcomes from one environment should not be read as representing production wallet behavior in another environment.