Bitcoin Address Format Evolution
Understanding Legacy, P2SH, SegWit & Taproot
Why Do Different Address Formats Exist?
Bitcoin addresses have evolved over time to improve efficiency, privacy, and functionality. Each new format introduces important benefits while remaining backwards-compatible with the network.
Interactive Address Comparison
See the same wallet seed generate different addresses for each format. All addresses below are derived from the same private key!
Master Seed (Example)
abandon abandon abandon abandon abandon abandon abandon abandon abandon abandon abandon about
This is a demo seed. Never use example seeds for real Bitcoin!
Legacy (P2PKH)
20091BvBMSEYstWetqTFn5Au4m4GFg7xJaNVN2
Format Details
- Prefix: Starts with "1"
- Script Type: Pay-to-PubKey-Hash
- Encoding: Base58Check
- Typical Size: ~230 vBytes
Advantages
- Universal compatibility
- Supported by all wallets
- Oldest, most tested
Disadvantages
- Highest transaction fees
- Larger transaction size
- No native SegWit benefits
When to Use
Only if receiving from very old wallets/exchanges that don't support newer formats. Generally avoid for new addresses.
P2SH (Nested SegWit)
20123J98t1WpEZ73CNmYviecrnyiWrnqRhWNLy
Format Details
- Prefix: Starts with "3"
- Script Type: Pay-to-Script-Hash
- Encoding: Base58Check
- Typical Size: ~170 vBytes
Advantages
- ~26% fee savings vs Legacy
- Enables multi-signature
- Wide compatibility
Disadvantages
- Still higher fees than native SegWit
- More complex scripts
- Being phased out
When to Use
Multi-signature wallets or when you need SegWit benefits but the sender doesn't support native SegWit (bc1...). Transitional format.
Native SegWit (P2WPKH)
2017 RECOMMENDEDbc1qw508d6qejxtdg4y5r3zarvary0c5xw7kv8f3t4
Format Details
- Prefix: Starts with "bc1q"
- Script Type: Pay-to-Witness-PubKey-Hash
- Encoding: Bech32
- Typical Size: ~141 vBytes
Advantages
- ~40% fee savings vs Legacy
- Case-insensitive (fewer errors)
- Better error detection
- Smaller transaction size
Disadvantages
- Some old wallets can't send to it
- Longer address (though easier to type)
When to Use
Default choice for most users! Best balance of fee savings, compatibility, and security. Use unless you have a specific reason not to.
Taproot (P2TR)
2021 NEWESTbc1p5cyxnuxmeuwuvkwfem96lqzszd02n6xdcjrs20cac6yqjjwudpxqkedrcr
Format Details
- Prefix: Starts with "bc1p"
- Script Type: Pay-to-Taproot
- Encoding: Bech32m
- Typical Size: ~110 vBytes
Advantages
- ~52% fee savings vs Legacy
- Enhanced privacy (multi-sig looks like single-sig)
- Advanced smart contract support
- Smallest transaction size
Disadvantages
- Newest - still gaining adoption
- Some wallets don't support yet
- More complex to implement
When to Use
Future-proof choice! Use when wallet supports it. Best for privacy-conscious users, advanced multi-sig, or maximum fee savings. Adoption growing rapidly.
Fee Comparison Calculator
See how much you can save by using modern address formats!
Annual Fee Comparison
Legacy (P2PKH)
P2SH
Native SegWit
Taproot
Key Insight
By switching from Legacy to Taproot, you save $550/year in fees!
Over 10 years at current Bitcoin price: $5,500 saved
Privacy Comparison
Legacy & P2SH
Single-sig and multi-sig transactions are easily distinguishable. Anyone can tell if an address is multi-sig by looking at the transaction.
- ✗ Multi-sig clearly identified
- ✗ Number of signatures revealed
- ✗ Script complexity exposed
Native SegWit
Better privacy through witness data separation, but multi-sig still distinguishable from single-sig.
- ✓ Witness data separated
- ✗ Still reveals multi-sig usage
- ✓ Slightly harder to analyze
Taproot
Game-changer! Multi-sig and single-sig transactions look identical. Complex smart contracts appear as simple payments.
- ✓ Multi-sig indistinguishable from single-sig
- ✓ Script paths hidden (Schnorr signatures)
- ✓ Maximum privacy for complex setups
Wallet Compatibility
Which address formats does your wallet support?
| Wallet | Legacy (1...) | P2SH (3...) | SegWit (bc1q...) | Taproot (bc1p...) |
|---|---|---|---|---|
| Bitcoin Core | ✓ | ✓ | ✓ | ✓ |
| Electrum | ✓ | ✓ | ✓ | ✓ |
| Ledger Hardware | ✓ | ✓ | ✓ | ✓ (2022+) |
| Trezor Hardware | ✓ | ✓ | ✓ | ✓ (2022+) |
| BlueWallet | ✓ | ✓ | ✓ | ✓ |
| Sparrow Wallet | ✓ | ✓ | ✓ | ✓ |
| Muun | ✓ | ✓ | ✓ | Partial |
| Old Wallets (pre-2017) | ✓ | ✓ | ✗ | ✗ |
Important: Most modern wallets (2020+) support all formats. If sending TO someone using an old wallet, they may not support SegWit/Taproot addresses.
Which Address Format Should I Use?
Answer these questions:
Key Takeaways
All From Same Seed
One wallet seed can generate addresses in ALL formats. Your private keys control Bitcoin, not the address format!
Fees Matter
Taproot saves up to 52% vs Legacy. Over years, this adds up to significant savings, hundreds or thousands of dollars!
Privacy Improves
Taproot makes multi-sig indistinguishable from single-sig. Better privacy for everyone, especially advanced users.
Use SegWit or Taproot
Default recommendation: Use Native SegWit (bc1q...) or Taproot (bc1p...) for new addresses. Legacy is obsolete.
Backwards Compatible
All formats work on the same Bitcoin network. You can send from any format to any other format without issues.
Future Is Taproot
Taproot adoption is growing fast. Expect it to become the standard as more wallets add support (already widespread in 2024+).
Final Recommendation
For most users: Use Native SegWit (bc1q...) as your default.
For advanced users or privacy-focused: Use Taproot (bc1p...) if your wallet supports it.
Avoid: Creating new Legacy (1...) addresses unless absolutely necessary for compatibility.