Bitcoin address types are foundational to how users interact with the blockchain, yet few appreciate the profound differences between legacy, nested, and native SegWit formats. P2PKH (Pay-to-Public-Key-Hash) addresses, introduced with Bitcoin’s inception, remain widely used despite newer formats promising efficiency and cost savings. Surprisingly, as of mid-2026, over 40% of Bitcoin transactions still originate from legacy addresses, highlighting a stubborn resistance to change among holders and service providers.
This article dissects the evolution from P2PKH to P2SH (Pay-to-Script-Hash) and the Bech32 native SegWit format, analyzing their technical trade-offs, adoption rates, and the often overlooked security implications. By challenging the assumption that newer address types have already dominated usage, we reveal the nuanced reality backed by on-chain data from Glassnode and usage trends from major wallets.
📊 KEY DATA
Legacy P2PKH Tx Share (2026)
P2SH Tx Share (2026)
Bech32 Tx Share (2026)
Fee Savings with Bech32 vs P2PKH
Why P2PKH Remains Entrenched Despite Its Inefficiencies
The P2PKH address type, characterized by its 1-prefixed format, is Bitcoin’s original address scheme. It encodes a hash of the user's public key and requires a single signature to unlock. While straightforward, it carries higher transaction sizes and fees compared to newer address schemes.
Legacy Compatibility and User Behavior
- Many wallets and exchanges still default to P2PKH for backward compatibility.
- Users unfamiliar with address formats stick to what they know to avoid errors.
- Hardware wallets historically supported P2PKH first, reinforcing its dominance.
On-chain data from Glassnode shows that even in 2026, a significant chunk of Bitcoin outflows originate from P2PKH addresses, despite the availability of cheaper alternatives.
The Rise of P2SH: Flexible Scripts and the Gateway to Multi-Sig
P2SH addresses, starting with a 3-prefix, introduced a way to pay to a script hash rather than a single public key hash. This innovation enabled complex spending conditions, including multisignature wallets and escrow scripts.
Why P2SH Gained Traction
- Enabled multi-signature wallets crucial for institutional custody.
- Allowed easier adoption of SegWit via nested P2SH addresses.
- Lower fees than P2PKH when used with SegWit, while preserving compatibility.
However, P2SH transactions remain larger and less cost-effective than native SegWit (Bech32) transactions. Still, as per CoinMarketCap’s educational resources, P2SH’s compatibility drove its adoption in wallets and exchanges reluctant to fully embrace Bech32.
Bech32: The Technological Leap Forward That’s Not Yet Universal
Bech32 addresses (bc1-prefixed) represent Bitcoin’s native SegWit format, offering the lowest transaction costs and improved error detection. Its lowercase alphanumeric format and checksum reduce user errors, but adoption remains partial.
Technical Advantages
- Lower transaction size reduces fees by 30-50% compared to P2PKH.
- Improved error detection reduces the risk of lost funds due to mistyped addresses.
- Designed to be future-proof for potential protocol upgrades.
Despite these benefits, many custodial services and legacy wallets have delayed full support, limiting Bech32’s market share. The bitcoin.org developer guides emphasize that wallet support is the key bottleneck, not protocol limitations.
Security Implications Across Address Types: Myths and Realities
A common assumption is that newer address types are inherently more secure. While Bech32’s design reduces user errors, the underlying cryptographic security remains primarily a function of the key management and script complexity.
Comparing Security Vectors
- P2PKH: Simple single-signature, vulnerable if private keys are mishandled.
- P2SH: Enables multi-signature and complex scripts, enhancing security for institutional use.
- Bech32: Adds error detection at the address level but depends on secure key management like others.
Ultimately, address type alone does not guarantee security; user and service provider practices remain paramount.
Comparing Bitcoin Address Types: Adoption, Cost, and User Experience
| Feature | P2PKH | P2SH | Bech32 |
|---|---|---|---|
| Address Prefix | 1 | 3 | bc1 |
| Transaction Size | Largest | Medium | Smallest |
| Fee Efficiency | Lowest | Better | Best |
| Multi-Sig Support | No | Yes | Yes |
| User Error Resistance | Low | Medium | High |
| Adoption (Tx Share 2026) | 40% | 35% | 25% |
Key Takeaways
- P2PKH remains widely used despite higher fees and larger transaction sizes, largely due to legacy wallet defaults and user familiarity.
- P2SH blended flexibility with compatibility, enabling multi-sig and nested SegWit adoption but at a cost premium over native SegWit.
- Bech32 offers the best cost efficiency and error resistance but faces adoption barriers from some custodians and wallets.
- Address type alone is not a security guarantee; proper key management and script complexity matter most.
- The transition to modern addresses is ongoing; understanding these types helps users optimize costs and security.
For developers and users aiming to optimize Bitcoin use, embracing Bech32 is a clear path forward, but awareness of legacy systems and gradual adoption realities is critical. Comprehensive on-chain data from Glassnode and authoritative insights from bitcoin.org remain invaluable resources for tracking this evolution.
Stay Ahead of the Market
Get daily crypto analysis, price breakdowns, and on-chain insights from Bitcoin Fast Community — updated 4x daily.
Read All Analysis →Free Tool
Bitcoin Halving 2028 Countdown
Track the exact countdown to the next halving and analyze historical post-halving price cycles.
Related Crypto Guides
Frequently Asked Questions
Q: What are the main differences between P2PKH, P2SH, and Bech32 addresses?
A: P2PKH addresses start with '1' and are the original Bitcoin addresses, requiring a signature from a single public key. P2SH addresses start with '3' and pay to a script hash, enabling multi-signature and complex scripts. Bech32 addresses start with 'bc1' and represent native SegWit, offering lower fees and better error detection. Each type differs in transaction size, fee efficiency, and script flexibility.
Q: Why do many users still use P2PKH despite its higher fees?
A: Legacy P2PKH addresses persist because many wallets and exchanges default to them for backward compatibility. Users often stick to familiar address formats to avoid mistakes. Hardware wallet support and custodial policies also contribute to the slow migration away from P2PKH.
Q: How does Bech32 improve transaction costs compared to older formats?
A: Bech32 addresses reduce transaction size by native SegWit encoding, leading to fee savings typically between 30-50% compared to P2PKH. This is due to better witness data structure and more efficient script verification, lowering the byte size of each transaction.
Q: Is Bech32 more secure than P2PKH or P2SH?
A: While Bech32 has improved error detection reducing the chance of address typos, its fundamental cryptographic security depends on key management like other types. P2SH can offer enhanced security through multi-signature scripts, so security depends more on wallet setup and user practices than address format alone.
Q: What is the adoption trend for these Bitcoin address types?
A: As of 2026, P2PKH accounts for about 40% of transactions, P2SH roughly 35%, and Bech32 around 25%. Despite Bech32’s technical advantages, adoption is gradual due to wallet support and user familiarity, with an ongoing shift expected as more services upgrade.