A Bitcoin address is a unique string of letters and numbers used to send and receive Bitcoin (BTC) on the blockchain. Similar to an email address, it acts as a destination for transactions. Bitcoin addresses are generated from public keys and vary in format based on the type of address used.
Different address types offer varying levels of efficiency, security, and transaction fees. There are currently four active Bitcoin address formats: Legacy (P2PKH), Nested SegWit (P2SH), Native SegWit (P2WPKH / Bech32), and Taproot (P2TR / Bech32m). Understanding the differences helps you choose the right format, avoid compatibility issues with exchanges, and minimize transaction fees.
Types of Bitcoin Addresses
Bitcoin addresses come in four active formats, each with distinct characteristics, fee profiles, and compatibility levels. The four types are Legacy (P2PKH), Nested SegWit (P2SH), Native SegWit (Bech32 / P2WPKH), and Taproot (Bech32m / P2TR). Each generation introduced lower fees, better efficiency, or new scripting capabilities.
Bitcoin Address Types at a Glance
๐ Quick takeaway: Native SegWit (bc1q) is the best choice for most users โ lowest fees and wide exchange support. Taproot (bc1p) offers the most advanced privacy and scripting but exchange support remains uneven.
| Address Type | Prefix | Encoding | Relative Fee | Best For | Exchange Support |
|---|---|---|---|---|---|
| Legacy (P2PKH) | 1 |
Base58 | ๐ด Highest | Maximum compatibility with old wallets and services | ๐ข Universal |
| Nested SegWit (P2SH) | 3 |
Base58 | โ ๏ธ Medium | Compatibility bridge; multi-signature setups | ๐ข Very wide |
| Native SegWit (P2WPKH) | bc1q |
Bech32 | ๐ข Low |
Everyday transactions; lowest fees on most wallets ๐ Best for most users |
๐ข Wide Some older services excluded |
| Taproot (P2TR) | bc1p |
Bech32m |
๐ข Lowest for complex scripts ๐ Most efficient for multi-sig and scripting |
Advanced scripting, privacy, multi-sig efficiency |
โ ๏ธ Growing but uneven Inconsistent across major exchanges as of 2024-2025 |
Legacy Addresses (P2PKH)
Legacy addresses, also known as Pay-to-PubKey Hash (P2PKH), are the original Bitcoin address format. They begin with the number 1 and are widely supported across all wallets and exchanges. However, they have higher transaction fees because they use more block space.
Legacy addresses use the most block space of any current format because they store the full public key hash and signature in the main transaction body rather than a separate witness field. This results in larger transaction sizes and therefore higher fees when the network is congested. Switching from a Legacy to a Native SegWit address for the same transaction type typically reduces transaction size by roughly 30-40%, translating directly to lower fees.
For example: 1A1zP1eP5QGefi2DMPTfTL5SLmv7DivfNa
Nested SegWit Addresses (P2SH)
Nested SegWit, or Pay-to-Script Hash (P2SH), is an improvement over Legacy addresses. These addresses begin with 3 and allow for complex scripts, such as multi-signature transactions. They offer reduced transaction fees compared to P2PKH but may not be supported by all wallets.
For example: 3J98t1WpEZ73CNmQviecrnyiWrnqRhWNLy
Native SegWit Addresses (Bech32)
Native SegWit addresses (P2WPKH) use Bech32 encoding and begin with bc1q. They provide lower transaction fees than Legacy or Nested SegWit formats and use a more human-readable, error-resistant format. Bech32 addresses reduce transcription errors and are fully compatible with the SegWit protocol. Note that Bech32 (bc1q) is distinct from Bech32m (bc1p), which is used exclusively for Taproot addresses.
For example: bc1qw508d6qejxtdg4y5r3zarvaryv7z6h78j8x3t4
Taproot Addresses (P2TR / Bech32m)
Taproot addresses, also called Pay-to-Taproot (P2TR), are the newest Bitcoin address format. They begin with bc1p and use the Bech32m encoding, a refinement of Bech32 introduced in BIP-350 to improve error detection for this format.
Taproot was activated on the Bitcoin network in November 2021 and has seen rapid adoption. By 2024, Taproot transactions accounted for roughly 40-42% of all Bitcoin transactions, driven in part by Ordinals and inscription activity as well as efficiency gains for multi-signature setups.
Key advantages of Taproot addresses include improved privacy (complex multi-signature transactions appear identical to single-key transactions on-chain), lower fees for complex scripts, and support for advanced scripting via Tapscript. However, support across exchanges and wallets remains uneven. As of 2024-2025, several major services including Binance, Coinbase, Gemini, and Strike had limited or delayed ability to send to bc1p addresses.
For example: bc1p5cyxnuxmeuwuvkwfem96lqzszd02n6xdcjrs20cac6yqjjwudpxqkedrcr

Which Bitcoin Address Type Is Best?
For most users making everyday transactions, Native SegWit (bc1q) offers the best combination of low fees and broad exchange support. If your wallet and all services you use support it, Taproot (bc1p) offers the lowest fees for complex scripts and better privacy, but verify exchange compatibility before using it as a deposit address.
Use this quick decision guide:
- Maximum compatibility needed: (older wallets, unknown services): Use Legacy (1…)
- Good compatibility, lower fees: Use Nested SegWit (3…)
- Best everyday choice: Use Native SegWit (bc1q…)
- Advanced use cases, privacy, multi-sig: Use Taproot (bc1p…) โ confirm exchange support first
If you are still using a Legacy address, generating a new Native SegWit address in a compatible wallet and moving your funds is straightforward and will reduce your future transaction fees.
How Bitcoin Address Types Evolved
Understanding the progression from Legacy to Taproot helps explain why newer formats exist and what problems each one solved.
- 009 โ P2PKH (Legacy): The original Bitcoin address format. Simple and universally supported, but uses the most block space and therefore incurs the highest fees.
- 2012 โ P2SH (Nested SegWit): Introduced via BIP-16 to support more complex scripts such as multi-signature transactions. Offered a compatibility bridge for SegWit adoption.
- 2017 โ P2WPKH (Native SegWit / Bech32): Introduced with the SegWit soft fork. Moves signature data to the witness field, reducing the effective size of transactions and lowering fees.
- 2021 โ P2TR (Taproot / Bech32m): Activated in November 2021. Combines Schnorr signatures and Tapscript to improve privacy, reduce fees for complex scripts, and enable more advanced smart contract capabilities. By 2024, Taproot accounted for roughly 40-42% of Bitcoin transactions.
FAQ
Can I send Bitcoin to any address type?
Most modern wallets support Legacy, Nested SegWit, and Native SegWit (Bech32 / bc1q) addresses. However, Taproot (Bech32m / bc1p) support is still uneven. As of 2024-2025, several major exchanges including Binance, Coinbase, Gemini, and Strike had limited or no ability to send to bc1p addresses. Always verify that your sending platform supports the destination address format before initiating a transaction.
Which Bitcoin address type is best?
Bech32 (bc1) addresses are the most efficient and cost-effective, but if compatibility is a concern, P2SH (3) addresses provide a good balance.
Can I convert my Legacy address to SegWit?
You cannot directly convert an old address, but you can generate a new SegWit address in a compatible wallet and transfer your funds.
Why do some Bitcoin addresses start with bc1, 1, or 3?
These prefixes indicate different address formats: Legacy (1), Nested SegWit (3), and Native SegWit (bc1).
Are Taproot addresses widely used?
Yes. Taproot (P2TR) adoption grew rapidly and by 2024 accounted for approximately 40-42% of all Bitcoin transactions, partly driven by Ordinals and inscription activity. However, exchange support remains uneven. As of 2024-2025, a number of major exchanges still had limited ability to send to bc1p (Taproot) addresses, so always verify your exchange supports the format before using it as a withdrawal destination.
What is the difference between Bech32 and Bech32m?
Bech32 (bc1q) is the encoding used for Native SegWit (P2WPKH) addresses. Bech32m (bc1p) is a refined encoding introduced in BIP-350 specifically for Taproot (P2TR) addresses. The two look similar but are technically distinct. A wallet or exchange must explicitly support Bech32m to send to a bc1p address.
Is it safe to send to a Taproot (bc1p) address from an older wallet?
Only if your wallet software explicitly supports Bech32m. Sending from an incompatible wallet may result in an error or failed transaction. Check your wallet’s release notes or support documentation before sending to a bc1p address for the first time.
How do Ordinals and inscriptions affect Taproot adoption?
Ordinals and Bitcoin inscriptions (NFT-like data inscribed on satoshis) rely on Taproot’s scripting capabilities. The surge in Ordinals activity in 2023-2024 significantly increased Taproot transaction volume, contributing to its rise to ~40-42% of all Bitcoin transactions by 2024.
