Base58 Address

Overview

Base58 encoding was designed to make long binary identifiers easier for people to copy and read. It removes characters such as zero, uppercase O, uppercase I, and lowercase l that are easily confused in many fonts.

Bitcoin legacy addresses use Base58Check rather than plain Base58. The encoded data includes a version byte indicating the network and address type, a payload such as a public-key hash or script hash, and a checksum derived from the data. This allows software to reject many mistyped strings.

Base58 addresses remain valid where the corresponding script type is supported, but newer Bitcoin outputs often use Bech32 or Bech32m. These formats provide different error-detection properties and make SegWit or Taproot address types clearer.

A Base58 string should not be treated as a universal crypto address. Other networks also use Base58, but with different payload lengths, prefixes, and semantics. Validation must always be network-specific.

Bitcoin Base58Check addresses commonly begin with characters associated with their network and script type, but the prefix alone is not sufficient validation. Decoding must verify the version byte, payload length, and checksum.

The format remains widely supported for legacy Bitcoin destinations, although native SegWit and Taproot use Bech32-family encodings. Base58 can be less efficient for QR codes because it mixes letter cases and does not offer the same error-location properties as newer formats. Applications should preserve support for legitimate legacy addresses while encouraging newer formats where compatibility allows. They should never transform a Base58 address by editing characters or prefixes manually.

Because Base58 strings are case-sensitive and visually dense, interfaces should support copy, paste, and QR scanning rather than encouraging manual entry.