Base58

Overview

Base58 encodes a large binary number using an alphabet of 58 characters. The common Bitcoin alphabet contains digits and upper- and lowercase letters but removes visually ambiguous characters. This makes strings easier to read, type, and transmit than long sequences of raw bytes while remaining compact enough for addresses and private-key export formats.

Encoding changes representation, not meaning. The input bytes are interpreted as a number and repeatedly divided by 58 to select output characters. Leading zero bytes require special handling so they are not lost during numeric conversion. Decoding reverses the process and reconstructs the original bytes. Unlike Binary Encoding or Hexadecimal, Base58 is not aligned to fixed groups of bits.

Plain Base58 does not detect typing errors. A character can be replaced with another valid character and still decode successfully to different bytes. Bitcoin commonly addresses this limitation with Base58Check, which adds version data and a checksum before encoding. Applications should distinguish the alphabet from the complete higher-level format.

Base58 is not a universal standard with one guaranteed alphabet. Different ecosystems can use different character orders or payload conventions. A decoder built for one system may produce an incorrect result for another even though the string appears valid. Software should use the encoding rules defined by the target protocol rather than a generic converter with unknown assumptions.

For payment systems, Base58 strings should be treated as structured protocol data. The application should decode the value, validate any version and checksum, and confirm that the result is allowed on the selected network. Visual readability reduces accidental mistakes, but it does not prove ownership, authenticity, or suitability for a particular transfer.