Crypto Gloss

Blockchain Address

A blockchain address is a unique alphanumeric string derived mathematically from a public key, used to receive cryptocurrency — analogous to a bank account number but without any name attached. Anyone can send funds to a public address; only the holder of the corresponding private key can spend them. On Bitcoin, addresses typically begin with “1” (legacy), “3” (P2SH), or “bc1” (Bech32/SegWit). On Ethereum, addresses are 42 characters beginning with “0x”. Despite their pseudonymous design, repeated address reuse can allow blockchain analytics firms to cluster addresses and link them to real identities.

How It Works

Address Generation

Addresses are derived via a one-way cryptographic process:

  1. Generate private key: A cryptographically secure random 256-bit number.
  2. Derive public key: Apply Elliptic Curve Digital Signature Algorithm (ECDSA) to the private key using curve secp256k1.
  3. Hash the public key: Apply SHA-256 then RIPEMD-160 hashing (Bitcoin) or Keccak-256 (Ethereum).
  4. Encode: Apply Base58Check encoding (Bitcoin) or hex with “0x” prefix (Ethereum).

The one-way nature of these functions means: given an address, you cannot derive the private key. Given a public key, you can derive the address. Given a private key, you can derive everything.

Bitcoin Address Formats

Format Prefix Standard Benefit
P2PKH (Legacy) 1… Original design Maximum compatibility
P2SH 3… BIP-16 Multi-sig, SegWit-wrapped
Bech32 (Native SegWit) bc1q… BIP-141 Lower fees, error detection
Taproot (Bech32m) bc1p… BIP-341 Privacy, Schnorr signatures

Ethereum Address Format

All Ethereum addresses are 20 bytes (40 hex characters) prefixed with “0x”:

  • Example: 0x742d35Cc6634C0532925a3b844Bc454e4438f44e
  • EIP-55 introduces mixed-case checksumming to detect typos.

HD Wallets and Derived Addresses

BIP-32/44 (Hierarchical Deterministic wallets) generate a tree of addresses from a single seed phrase. Modern wallets automatically derive a new receiving address for each transaction, improving privacy by preventing address reuse clustering.

Address Reuse: A Privacy Problem

When you reuse the same address to receive multiple payments:

  • All payments are publicly linked on the blockchain
  • The total balance at that address is visible to everyone
  • Blockchain analytics firms can cluster your activity to identify you

Best practice: use a new address for each receipt. Most modern wallets do this automatically.

Vanity Addresses

A vanity address is one that begins with a specific desired string (e.g., 1Bitcoin...). Generated by brute-force searching millions of key pairs — computationally expensive but does not weaken security if generated correctly. Online vanity address generators are a security risk (the website could log your private key).

History

  • 2009 — Bitcoin genesis: The first Bitcoin address (Satoshi’s) receives the 50 BTC genesis block reward.
  • 2012 — BIP-32 (HD wallets): Pieter Wuille proposes hierarchical deterministic key derivation — enabling one seed phrase to generate unlimited addresses.
  • 2013 — BIP-43/44: Standardizes HD wallet derivation paths, enabling cross-wallet seed phrase compatibility.
  • 2017 — Bech32 (SegWit addresses): Native SegWit addresses (“bc1”) launch with lower fees and built-in error detection; become the standard by 2022.
  • 2021 — Taproot addresses: “bc1p” addresses launch with Taproot activation, improving privacy for multi-sig and complex script users.
  • 2020 — Ledger breach: 272,000 physical addresses and 1M email addresses of hardware wallet customers leaked — not crypto addresses, but highlighting the privacy cost of attaching identity to crypto use.

Common Misconceptions

  • “Crypto accounts are anonymous.” Crypto addresses are pseudonymous, not anonymous. Every transaction is permanently public. With enough behavioral data, addresses can be deanonymized.
  • “Sending to the wrong address means the money is lost.” This is often true on most blockchains — transactions are irreversible. Address format checking (checksums) reduces but does not eliminate human error risk.
  • “My address is my wallet.” An address is a destination, not a wallet. Your wallet manages the private keys that control all your addresses.
  • “One person = one address.” A single user typically controls hundreds or thousands of addresses through HD wallet derivation.

Criticisms

  • Irreversibility of errors: Sending to a wrong or non-existent address results in permanent loss. Unlike bank transfers, there is no recourse mechanism.
  • Privacy by default is weak: Bitcoin and Ethereum’s transparent ledgers make financial history publicly visible without deliberate privacy practices (using new addresses, CoinJoin, etc.).
  • Format complexity: Multiple address formats (legacy, SegWit, Taproot on Bitcoin; ENS vs. hex on Ethereum) create user confusion and interoperability issues.
  • Long address strings: The length and complexity of blockchain addresses creates friction vs. traditional payment systems, contributing to usability barriers.

Social Media Sentiment

Address-related discussions are common on r/Bitcoin and r/ethereum, particularly around format migrations (SegWit adoption, Taproot), privacy best practices, and recovery from sending to wrong addresses. ENS (Ethereum Name Service) — which maps addresses to human-readable names — is popular on r/ethereum as a usability improvement.

Active communities: r/Bitcoin, r/ethereum, r/CryptoCurrency, r/BitcoinBeginners

Last updated: 2026-04

Related Terms

See Also

Sources