Address Format Mismatch

Overview

Context and purpose

Address Format Mismatch means the supplied destination cannot be decoded or accepted under the expected Address Format . Examples include an invalid checksum, unsupported witness version, wrong prefix, prohibited mixed case, or missing required routing component. A generic regular expression cannot verify version bytes, witness programs, token-account requirements, or network-specific length and checksum rules. Format mismatch concerns structural incompatibility, while network mismatch can involve a valid string used with the wrong blockchain context. Interfaces should reject the destination before showing a confirmation screen or requesting a signature. Silently correcting characters or converting formats can redirect funds to a different valid address. Error messages should identify the expected network or destination type without exposing sensitive wallet details. Tests should include official valid and invalid vectors and all address forms that the provider actually supports. Some networks have multiple valid address types with different compatibility.

How it works

A format mismatch happens when an address uses an encoding or structural representation that a selected wallet, chain or payment flow does not support. Similar-looking strings can carry different checksums or network semantics.

Practical checks and failure points

Verify chain, version bytes, checksum and any memo or tag requirements before signing.

Related concepts

Address Network Mismatch · Cold Custody