AI disclosure: drafted by Basis Desk's AI newsroom and machine-checked against the primary sources listed below — how we use AI. Originally published on Basis Desk.
An overview of Bitcoin address formats, detailing how encoding and script types dictate transaction fees, privacy features, and wallet compatibility.
Key points
- Legacy addresses begin with '1' and require the most data, resulting in higher transaction fees.
- P2SH addresses begin with '3' and allow for complex scripts, including multisig and nested SegWit.
- Native SegWit (bc1q) separates signature data, offering roughly a 38% fee reduction over Legacy.
- Taproot (bc1p) uses Schnorr signatures to aggregate complex transactions, improving privacy and block efficiency.
A Bitcoin address serves as an instruction manual for how funds are locked and subsequently unlocked on the network. Over time, the $BTC protocol introduced new address formats—spanning from original Legacy designs to SegWit and Taproot—to optimize block space, reduce transaction fees, and improve privacy. Users and institutions navigating these formats must weigh fee efficiency against software compatibility.
Legacy Addresses: The Original Standard
The first iteration of Bitcoin addresses, known as Legacy or Pay-to-Public-Key-Hash (P2PKH), begins with the number "1". This format was the default standard for the first several years of the network's existence. Legacy addresses use Base58Check encoding, which includes a checksum to prevent typographical errors but is case-sensitive, making it prone to human error during manual transcription.
Transactions originating from Legacy addresses are the most data-intensive. When spending funds from a P2PKH address, the user must reveal their public key and a cryptographic signature within the transaction data. Because Bitcoin block space is strictly limited, the larger data footprint of Legacy transactions translates directly to higher network fees. Consequently, most modern wallet infrastructure has migrated away from generating new "1" addresses, though they remain fully supported by the consensus rules for receiving and sending funds.
Pay-to-Script-Hash (P2SH): Enabling Complexity
Addresses beginning with the number "3" rely on the Pay-to-Script-Hash (P2SH) standard. Introduced to shift the burden of data storage from the sender to the recipient, P2SH allows users to lock funds in a script that requires specific conditions to be met before the funds can be moved.
Initially, P2SH addresses were predominantly used for multi-signature (multisig) wallets, where multiple private keys are required to authorize a transaction. Later, P2SH served a critical transitional role for the Segregated Witness (SegWit) upgrade. By nesting a SegWit script inside a P2SH address, developers created a backward-compatible format known as Nested SegWit. This allowed older wallets that did not understand native SegWit to send funds to SegWit-enabled wallets, reducing fees slightly compared to purely Legacy transactions while maintaining broad compatibility.
Native SegWit: The Efficiency Upgrade
Introduced in 2017, Native SegWit (Pay-to-Witness-Public-Key-Hash or P2WPKH) addresses begin with "bc1q". This upgrade fundamentally altered how transaction data is structured by separating, or segregating, the cryptographic signature (the witness data) from the transaction data.
Native SegWit addresses utilize Bech32 encoding. Unlike Base58Check, Bech32 is exclusively lowercase, eliminating confusion between similar-looking characters like "O" and "0" or "I" and "l". The primary advantage of Native SegWit is cost reduction. Because witness data is weighed differently by the Bitcoin protocol—enjoying a 75% discount in terms of block weight—transactions originating from "bc1q" addresses require significantly lower fees.
Taproot: Privacy and Advanced Scripting
Activated in 2021, the Taproot upgrade introduced addresses beginning with "bc1p". This format uses a modified encoding scheme called Bech32m, designed to fix a minor vulnerability found in the original Bech32 standard. For further reading on the cryptographic mechanisms behind this upgrade, see Bitcoin Taproot, Explained: Schnorr Signatures and MAST.
Taproot leverages Schnorr signatures, which allow for signature aggregation. In a standard multisig transaction using older address types, every participant's signature must be published to the blockchain, consuming block space and revealing the governance structure of the wallet. With Taproot, multiple signatures can be aggregated into a single signature. This makes complex transactions—such as lightning network channel openings or institutional multisig operations—look identical to standard, single-signature transactions on the public ledger. This upgrade improves both privacy and data efficiency for complex smart contracts on the Bitcoin network.
Transaction Fees and Address Types
The most tangible impact of address types for end-users is transaction pricing. Bitcoin miners prioritize transactions based on the fee paid per unit of data (measured in satoshis per virtual byte, or sat/vB). Because different address types require different amounts of data to unlock funds, the address type directly dictates the cost to send $BTC.
Consider a standard transaction scenario: sending funds from a single input to two outputs (one destination address and one change address back to the sender).
Assuming a network fee rate of 20 sat/vB:
- A Legacy (P2PKH) transaction has a size of approximately 226 vBytes. The total fee would be 4,520 satoshis.
- A Native SegWit (P2WPKH) transaction has a size of approximately 140.5 vBytes. The total fee would be 2,810 satoshis.
In this example, utilizing Native SegWit results in a fee reduction of roughly 38% compared to Legacy infrastructure. As network congestion rises and fee rates increase, the absolute cost savings associated with efficient address types become significantly larger, driving institutional and retail migration toward "bc1q" and "bc1p" formats.
Common misconceptions
- Address formats dictate network isolation: It is a common misunderstanding that Native SegWit or Taproot addresses operate on a different network. All standard address types are cross-compatible at the protocol level; a Legacy address can send funds to a Taproot address, and vice versa. Compatibility issues only arise when a specific wallet or exchange software has not updated its user interface to recognize newer prefix formats.
- Newer addresses are less secure: Some users assume that cryptographic discounts on witness data or new signature schemes compromise security. The security models for P2WPKH and P2TR are mathematically robust and have been rigorously vetted by the Bitcoin development community.
- Reusing addresses is required: While addresses can technically receive multiple transactions, address reuse degrades privacy for both the sender and the receiver by linking financial histories. Modern hierarchical deterministic (HD) wallets generate a new address for every transaction automatically, regardless of whether they use Legacy or SegWit formats.
How this connects to the market
The adoption of efficient address types acts as a barometer for institutional infrastructure upgrades and network health. Exchanges and custodians processing thousands of daily withdrawals face immense operational costs during periods of high network congestion. By upgrading backend systems to Native SegWit or Taproot, institutions drastically reduce overhead, which often translates to lower withdrawal fees for retail clients.
Furthermore, the proliferation of Taproot (bc1p) addresses is closely monitored by market analysts as a proxy for advanced network usage. Because Taproot enables more efficient multisignature setups and arbitrary data inscription, spikes in Taproot adoption often correlate with the deployment of new institutional custody arrangements or waves of activity in on-chain assets and protocols built atop the base layer.
FAQ
Can a Legacy address send Bitcoin to a Taproot address?
Yes. All standard Bitcoin address types are cross-compatible on the blockchain. Any limitations are strictly due to the specific software or exchange being used, not the Bitcoin protocol itself.
Why are Native SegWit addresses lowercased?
Native SegWit addresses use Bech32 encoding, which relies on a specific 32-character alphabet consisting entirely of lowercase letters and numbers. This design eliminates visual ambiguity and reduces transcription errors.
Do I need to migrate my old Bitcoin to a new address format?
No action is strictly required. Funds held in Legacy addresses remain secure and spendable. However, moving them to a SegWit or Taproot address will lower the fees incurred when you eventually spend those funds in the future.
Sources
- Bitcoin Developer Reference: Transactions — Bitcoin.org
- BIP 341: Taproot: SegWit version 1 spending rules — Bitcoin Improvement Proposals
Basis Desk is a source-verified crypto newsroom. Market data, a free MCP server for AI agents and JSON APIs: basisdesk.news/developers. Not investment advice.
Top comments (0)