Insights on Crypto Payments, Infrastructure, and Operations

Address Format

Crypto & Blockchain Fundamentals

Pronunciation: AD-dress FOR-mat

Also known as: Blockchain Address Format, Crypto Address Format

Definition

Address format is the protocol-defined structure and encoding of a blockchain address, including its prefix, version, character set, length, payload, and error-detection rules. A format can reveal whether the destination is for mainnet or testnet and may indicate a script or witness version. Compatibility varies, so a network may accept an address type that an older wallet or.

Overview

Contents Hide
  1. Understand the idea
  2. What actually happens
  3. Decisions and failure cases
  4. Related concepts
  5. Further reading

Understand the idea

A blockchain does not recognize an address merely because it looks like a random string. Each supported address format encodes protocol-specific information. This may include a network marker, address or script type, witness version, public-key hash, contract identifier, or checksum.

Bitcoin illustrates how several formats can coexist. Legacy Base58Check addresses represent older script types, Bech32 is used for native SegWit version 0 outputs, and Bech32m is used for later witness versions such as Taproot. Other networks use hexadecimal addresses, base58 encodings, human-readable prefixes, fixed-length byte values, or checksummed capitalization.

What actually happens

An address format is the encoding and validation convention a blockchain uses for destinations. Its alphabet, checksum, length and prefix can help software reject mistyped data, but they do not always identify one unique network. Some Ethereum-compatible chains use the same 20-byte account-address representation. Conversely, Bitcoin offers multiple address encodings tied to spending scripts and capabilities.

Address validation should parse the data, check any checksum, identify the expected network or chain ID and verify the destination type supported for that asset. For a token payment, a valid address alone is insufficient: the contract and chain must also match. Some networks require an additional memo or tag for deposits to pooled accounts. On Solana, associated token-account requirements introduce a different account-matching problem from an EVM native transfer.

Decisions and failure cases

Avoid truncating addresses into only a few visible characters during high-value confirmation; address-poisoning attacks exploit that habit. A syntactically valid string can still be the wrong person, chain or asset route. Checksum rules vary and may be optional in some wallets; never treat a passing format check as proof of ownership.

Address Prefix, Bech32m Address, Bech32 Address.

Further reading

Ethereum: Gas and Fees.

Example

A merchant presents a Bitcoin Bech32 address starting with 'bc1'. A customer pastes an address with a different network prefix. The wallet should warn or refuse rather than silently convert it. For an EVM address, a checksum may reduce typing mistakes but cannot distinguish Ethereum mainnet from BNB Smart Chain.

Comparison

Address format answers whether a string conforms to an encoding. Address ownership, network compatibility and payment intent require different checks.

Key Takeaway

Address format is the protocol-defined structure and encoding of a blockchain address, including its prefix, version, character set, length, payload, and error-detection rules.

Sources

  1. Bitcoin Developer Reference: Transactions — Bitcoin Developer Documentation (2026-08-02)
  2. BIP 173: Base32 Address Format for Native Witness Outputs — Bitcoin Improvement Proposals (2026-08-02)
  3. BIP 350: Bech32m Format for Witness Version 1 and Later — Bitcoin Improvement Proposals (2026-08-02)