Checksum
Pronunciation: CHECK-sum
Also known as: Error-Detection Checksum
Definition
A checksum is a value calculated from data and stored or transmitted with it so software can detect many accidental changes during copying, storage, or transmission. Blockchain systems use checksums in addresses, encoded keys, messages, and files. A matching checksum supports data integrity, but it is not a digital signature and does not prove who created the data or whether it is safe.
Overview
Meaning and scope
A checksum is a value calculated from data and stored or transmitted with it so software can detect many accidental changes during copying, storage, or transmission. Blockchain systems use checksums in addresses, encoded keys, messages, and files. A matching checksum supports data integrity, but it is not a digital signature and does not prove who created the data or whether it is safe.
Mechanism and operation
Checksum adds redundant information derived from the original data. A verifier recalculates the value and compares it with the supplied checksum. The exact algorithm and checksum length determine which error patterns can be detected. Base58Check appends checksum bytes before Base58 encoding, while Bech32 and Bech32m use specialized character-level checksum constructions. These mechanisms help wallets reject malformed addresses before a transaction is signed. An adversary can generate a different valid address with a correct checksum. For authentication and tamper resistance against intentional changes, systems use cryptographic signatures, message authentication codes, or trusted hash commitments.
Practical payment example
An address parser detects a typing error through a checksum before a merchant displays destination instructions, reducing—but not eliminating—wrong-address risk.
Operational checks
Checksums can also fail when software applies the wrong format. A string may have a valid checksum under one network or version but still be unsuitable for the selected asset. Validation must decode the complete structure and inspect network, type, and payload rules rather than treating checksum success as a universal approval.
Distinctions and limits
If they differ, the data has been corrupted, mistyped, or encoded incorrectly. A checksum is not designed to stop an attacker who can modify both the data and checksum. In operations, checksum failures should be reported as input or transport errors and should stop processing before funds move.
Related reading
Related definitions: Base58Check, Bech32.
Example
An address parser detects a typing error through a checksum before a merchant displays destination instructions, reducing—but not eliminating—wrong-address risk.
Comparison
If they differ, the data has been corrupted, mistyped, or encoded incorrectly. A checksum is not designed to stop an attacker who can modify both the data and checksum. An adversary can generate a different valid address with a correct checksum.
Key Takeaway
A checksum detects many accidental data errors, but it does not authenticate the sender, establish intent, or make a valid-looking destination trustworthy.
Sources
- Bitcoin Developer Reference: Transactions — Bitcoin Developer Documentation (2026-08-02)
- BIP 173: Base32 Address Format for Native Witness Outputs — Bitcoin Improvement Proposals (2026-08-02)
- BIP 350: Bech32m Format for Witness Version 1 and Later — Bitcoin Improvement Proposals (2026-08-02)