Skip to main content
Public-key cryptography

What is a Crypto Address? A Complete Beginner's Guide

Pomegra Learn

What is a Crypto Address?

A crypto address is a unique identifier on a blockchain that works like a bank account number or email address. It's where you receive cryptocurrency from others, and it's publicly visible on the blockchain. Unlike a bank account number, though, you can create unlimited addresses, they require no registration with any company, and they're secured by the mathematics of cryptography rather than institutional policies.

Quick definition: A crypto address is a string of alphanumeric characters (often appearing as a QR code) derived from your public key, serving as the destination where others send you cryptocurrency. It's public, shareable, and safe to display openly.

Key Takeaways​

  • A crypto address is derived from your public key and serves as your public identifier on a blockchain
  • Different blockchains use different address formats; a Bitcoin address cannot receive Ethereum and vice versa
  • Bitcoin addresses start with 1, 3, or bc1 and are case-sensitive, encoded in Base58Check
  • Ethereum addresses start with 0x and are case-insensitive (though checksummed formats exist)
  • You can generate unlimited addresses from the same private key using a hierarchical deterministic (HD) wallet
  • Sharing your address with anyone is safe; the address alone grants no spending power
  • Sending crypto to an invalid or wrong address results in permanent loss; always verify before confirming

Understanding Addresses and Public Keys​

Your public key is the mathematical foundation of your address. However, most blockchain systems add an extra layer: they hash your public key to create a shorter, more convenient address.

Bitcoin's approach: Your public key (65 or 33 bytes) is hashed using SHA-256 and RIPEMD-160, then encoded into a standard address format. This creates a shorter identifier (approximately 26–35 characters) that's easier to write, scan, or speak aloud than a raw public key.

Ethereum's approach: Your public key is hashed using Keccak-256, and the last 20 bytes become your address. Ethereum addresses are always prefixed with "0x" and are 40 characters long (plus the prefix).

The address, in either case, is a one-way derivation from your public key. Someone knowing your address cannot reverse-engineer your public key (though Ethereum's transparent blockchain means any outgoing transaction reveals your public key anyway). The address is the practical, user-friendly face of your public key.

Bitcoin Addresses: Three Formats​

Bitcoin has evolved to support three address formats, each offering different advantages.

P2PKH (Pay-to-Public-Key-Hash) — Legacy Addresses

These start with 1 and are the original Bitcoin address format. Example: 1A1z7agoat4wrMSEYstChZessCheEuxjGJ

Format:

  • 26–35 characters
  • Case-sensitive
  • Encoded in Base58Check (uses 0–9 and A–Z, excluding easily confused letters like 0, O, I, l)
  • Checksum built in; typos are usually caught
  • Slower and larger transactions in byte size

Base58Check includes a checksum—the last few characters are mathematically derived from the preceding ones. If you mistype a single character, the address becomes invalid, and your wallet will reject it. This checksum feature is a safety mechanism unique to Bitcoin.

P2SH (Pay-to-Script-Hash) — Script Addresses

These start with 3 and were introduced to allow complex transaction rules. Example: 3J98t1WpEZ73CNmYviecrnyiWrnqRhWNLy

Format:

  • Same length and encoding as P2PKH
  • Also case-sensitive with Base58Check checksum
  • Allow multisignature wallets (requiring multiple keys to spend)
  • Support advanced spending conditions
  • Still widely used by exchanges and custodians

Bech32 (SegWit) — Native Segwit Addresses

These start with bc1 and are the newest format. Example: bc1qar0srrr7xfkvy5l643lydnw9re59gtzzwf5mdq

Format:

  • Case-insensitive
  • More efficient encoding (Bech32)
  • Smaller transaction size, lower fees
  • Faster validation
  • Better error detection than Base58Check
  • Increasingly supported by wallets and exchanges

All three formats are valid Bitcoin addresses. Your private key can control any of them. Most modern wallets generate Bech32 addresses by default, but you should be able to receive Bitcoin at any of the three formats.

Ethereum Addresses: The 0x Standard​

Ethereum uses a different system entirely. Every Ethereum address starts with 0x and is followed by 40 hexadecimal characters (0–9, A–F), totaling 42 characters.

Example: 0x742d35Cc6634C0532925a3b844Bc029e4a72c5d1

Key characteristics:

  • Always 42 characters (including the 0x prefix)
  • Hexadecimal encoding (base 16)
  • Case-insensitive, but checksummed versions exist using EIP-55
  • One address format for all transactions (no legacy, P2SH, or Segwit variants)
  • Derived from the last 20 bytes of the Keccak-256 hash of your public key

EIP-55 Checksum Format:

Modern Ethereum wallets often use a checksummed format where uppercase and lowercase letters encode the checksum. Example: 0x742d35Cc6634C0532925a3b844Bc029e4a72c5d1

This format is case-sensitive. The capitalization pattern is generated from a checksum of the address. If you mistype the capitalization, the address is still technically valid, but most wallets will warn you. Strictly speaking, Ethereum addresses aren't case-sensitive, but the checksum feature acts as a typo detector, similar to Bitcoin's checksum.

Why Addresses Differ Across Blockchains​

Bitcoin and Ethereum use different cryptographic hash functions and encoding methods. This isn't accidental; each blockchain made design choices suited to its architecture.

Bitcoin chose:

  • RIPEMD-160 hashing (produces smaller addresses)
  • Base58Check encoding (human-readable, built-in checksum)
  • Multiple address formats to support different transaction types

Ethereum chose:

  • Keccak-256 hashing (same function used elsewhere in Ethereum)
  • Hexadecimal encoding (simpler, aligns with EVM architecture)
  • A single address format for all transactions

Other blockchains (Litecoin, Dogecoin, Ripple, Stellar, Monero) use their own formats too. A Litecoin address, even though it uses Bitcoin's same cryptographic approach, has a different version byte and looks distinctly different.

Critical rule: Never send one cryptocurrency to another blockchain's address format. Sending Bitcoin to an Ethereum address or vice versa results in permanent loss. Most modern wallets prevent this by validating the address format before allowing the send, but it's a common mistake with catastrophic consequences.

Generating Addresses: The Hierarchical Deterministic Wallet​

Modern cryptocurrency wallets don't just manage one private key and one address. Instead, they use a system called Hierarchical Deterministic (HD) wallets to generate unlimited addresses from a single seed phrase.

How it works:

  1. Your wallet starts with a seed phrase (usually 12 or 24 words)
  2. The seed is mathematically converted into a master private key
  3. The master private key generates child private keys through a deterministic process
  4. Each child private key generates its own address
  5. All addresses remain under your control—they're all derived from the same seed

Why generate multiple addresses?

  • Privacy: Each transaction uses a fresh address, making it harder to link transactions to you
  • Organization: You can label addresses for different purposes (business, personal, charitable donations)
  • Security: A compromised address doesn't compromise others (though someone seeing one public key can sometimes derive others in legacy systems)
  • Compatibility: Your wallet can receive from multiple addresses and track all balances

The BIP-32 standard (Hierarchical Deterministic Wallets) is widely used in Bitcoin wallets. The BIP-39 standard defines the 12 or 24-word seed phrase format. Ethereum and other blockchains have adopted similar patterns.

Addresses and Privacy​

An important caveat: while an address alone is public, it reveals your transaction history. On a transparent blockchain like Bitcoin or Ethereum, anyone can query the blockchain and see:

  • All transactions to or from an address
  • The current balance
  • The transaction history and timestamps
  • Amounts sent and received

If you publicly associate your name or email with an address, your entire financial history becomes traceable. This is why privacy-conscious users generate new addresses for each transaction and never reuse them.

Some blockchains (Zcash, Monero) offer privacy features that hide transaction details. But Bitcoin and Ethereum offer pseudonymity, not anonymity—your address is a pseudonym, but it can potentially be linked back to your identity through other means.

Best Practices for Using Addresses​

Always verify addresses before sending.

Malware can replace copied addresses with attacker addresses. Manually type the first and last characters of an address, or scan QR codes from trusted sources. Even a single character difference results in lost funds.

Never reuse addresses (ideally).

Generate a fresh address for each transaction in privacy-conscious scenarios. Most modern wallets handle this automatically.

Backup your seed phrase, not individual addresses.

If you have your seed phrase, you can regenerate all addresses. But if you lose the seed phrase and only have one address, you can receive but cannot spend from older addresses.

Distinguish between addresses and exchanges.

Your wallet address is different from an exchange account number. Your exchange account is a login credential; your wallet address is the public blockchain identifier. If you give someone your exchange login, they can control your funds. Your exchange address is just a label—real crypto lives on your private wallet.

Be aware of address reuse risks.

Some research suggests that reusing an address repeatedly (especially on Ethereum) can expose your public key. While not an immediate threat, best practice is to use a fresh address for each transaction or, at minimum, move all funds before reusing an address in the same wallet.

Real-World Examples​

Example 1: Receiving Bitcoin from a Friend

You give your friend a Bitcoin address: bc1qax0z94f8z4ae5x3c6l0z9a1z3a1z3a1z3a1z3

Your friend opens her Bitcoin wallet, pastes your address, and enters the amount. The wallet displays your address for confirmation. She clicks "Send." The transaction broadcasts to the Bitcoin network. Miners include it in a block, and you receive Bitcoin at your address.

Your friend never needed your private key—just your address. If the address was correct, the Bitcoin arrives safely.

Example 2: Organizing Finances with Multiple Addresses

You run a small business. You generate separate addresses for:

  • Customer payments (business address 1)
  • Payroll (business address 2)
  • Personal savings (personal address 1)
  • Charitable donations (charity address 1)

All addresses are derived from your single seed phrase. Your accounting software tracks balances at each address separately. You can send invoices with specific business addresses, making it easy to track which customers paid and when.

Example 3: The Address Typo Disaster

You want to send 5 ETH to a recipient. You manually type their Ethereum address but mistype the last character. Your wallet shows the balance will decrease, and you confirm the transaction. The ETH is sent to an invalid address—one that no one owns. The ETH is lost forever. No refund is possible; no one can recover it.

This is why address validation (entering it twice, using QR codes, or copying from trusted sources) is critical.

Common Mistakes to Avoid​

Mistake 1: Assuming addresses are interchangeable across blockchains. Bitcoin addresses receive Bitcoin only. Ethereum addresses receive Ethereum and ERC-20 tokens only. Sending the wrong asset to an address results in permanent loss. Always verify the blockchain before sending.

Mistake 2: Trusting an address you found on Google. Attackers create fake websites and show addresses controlled by them. If you search "Bitcoin address example," you might get an attacker's address. Only use addresses you've generated yourself or received directly from the owner (through phone call, in-person meeting, or verified email).

Mistake 3: Reusing the same address for years. While not always dangerous, it reduces privacy and violates best practices in some contexts. Rotate to fresh addresses periodically.

Mistake 4: Storing addresses in unsecured locations. You can share your address safely, but if an attacker sees it and can link it to your identity, your financial history is exposed. For privacy, keep addresses separate from personal information.

Mistake 5: Confusing an address with a private key. If someone asks for your address, they're asking for something safe to share. If they ask for your private key or seed phrase, it's a scam. Never confuse these.

FAQ​

Can I change my address? No, but you can generate a new one. Your old address remains valid forever; you just stop using it if you choose. All addresses derived from your seed phrase are permanently under your control.

If I send crypto to the wrong address, can it be recovered? Only if the address belongs to someone willing to help. If the address is invalid (doesn't exist), the funds are lost. If it's a valid address belonging to someone else, they could potentially return it, but they have no obligation to. The blockchain has no refund mechanism.

Are short addresses more secure than long addresses? No. Bitcoin addresses are 26–35 characters; Ethereum addresses are 42 characters. The length is determined by the hashing and encoding scheme. Security comes from the cryptography, not address length.

Can I have the same address on Bitcoin and Ethereum? No. Bitcoin and Ethereum use different derivation and hashing methods. The same private key produces different addresses on each blockchain. But some addresses might coincidentally look similar.

Should I memorize my address? You don't need to. Your wallet software stores and generates addresses from your seed phrase. If you want to be cautious, memorize your seed phrase, not individual addresses.

What if I give someone my address by mistake when they asked for my private key? That's actually the safe outcome. Your address is meant to be public. The person now has information that doesn't grant them access to your funds. No harm done.

Why do some addresses start with different characters? Different address types, blockchains, and encodings produce different prefixes. Bitcoin legacy addresses start with 1; P2SH addresses start with 3; Bech32 addresses start with bc1. Ethereum addresses always start with 0x. These prefixes help identify the address type and prevent mistakes.

Summary​

A crypto address is your public blockchain identifier—a unique, shareable string derived from your public key. Bitcoin and Ethereum use different address formats reflecting their different cryptographic designs. Bitcoin offers three formats (legacy, P2SH, Bech32); Ethereum uses a single format starting with 0x. You can generate unlimited addresses from a single seed phrase using HD wallets, allowing you to organize finances and improve privacy. Sharing your address is safe; it grants no spending power. But sending to an invalid or wrong address results in permanent loss, so always verify carefully. Master addresses, and you've mastered a fundamental aspect of blockchain interaction.

Next​

Continue to Digital Signatures for Beginners to learn how addresses prove ownership and authorize transactions on the blockchain.