Base58Check

Overview

Base58Check is a structured use of Base58, not merely a different alphabet. A typical Base58Check value contains a version byte or prefix, the actual payload, and checksum bytes derived from hashing the preceding data. The combined byte sequence is then encoded with the Base58 alphabet for human-readable use.

During decoding, software converts the characters back to bytes, separates the checksum, recalculates it from the version and payload, and compares the result. A mismatch indicates that the string is malformed or has likely been mistyped. The version information helps distinguish address or key types, while the checksum provides limited Data Integrity protection for the encoded text.

Bitcoin uses Base58Check for legacy P2PKH and P2SH address forms and for private keys exported in Wallet Import Format. The same encoding mechanism can carry different payloads, so applications must inspect the version rather than assuming every valid string is a payment address. A private-key string and an address can both pass checksum validation while representing very different objects.

The checksum is designed for accidental corruption, not adversarial authentication. An attacker can generate a different valid Base58Check string with a correct checksum. It also cannot determine whether the destination is controlled by the intended person. Payment software must still apply Address Format rules, network selection, recipient verification, and any policy controls.

Newer Bitcoin witness addresses generally use Bech32 or Bech32m instead of Base58Check. Services often support several formats at once for compatibility. Correct implementations decode each format with the appropriate standard and never convert an address merely to make its appearance consistent.