Bitcoin address formats: Legacy, SegWit and Bech32
Anyone who has sent or received cryptocurrency knows the specific anxiety of looking at a long string of random letters and numbers. One wrong character, and the funds dissolve into the blockchain with no way to cancel the transaction or ask support to undo it.
On the Quantum exchange people regularly hit a paradox: an address for the same asset, bitcoin, can start with 1, with 3, or with the letters bc1. Modern mobile and hardware wallets also show a completely new address after every incoming transaction. The obvious question follows: "Where did my old address go, and will funds still arrive there?"
A Bitcoin address is not a random string. It is the result of years of engineering on the protocol. Each prefix is a generation of the technology, and that generation sets the network fee, how heavy the transaction is, and how much of your financial history a stranger can see.
This guide goes through every address format of the first cryptocurrency, the real differences, which option is the practical one for a transfer, and the question of reusing an address.
What a Bitcoin address actually is
In a traditional bank we are used to one account: a card number or an IBAN that does not change. Salaries arrive there for years, purchases are paid from it, and it is tied to personal data.
Bitcoin is built differently. A Bitcoin address is a public cryptographic identifier, an encoded form of your public key or locking script.
As a physical picture, a Bitcoin address is a transparent one-time letterbox with a narrow slot:
- Anyone in the world who knows the box can drop coins into it.
- Through the transparent walls anyone can see how much is inside.
- Only the person with the unique physical key can open the door and take the contents. That key is your private key.
Because Bitcoin was designed around decentralisation, reliability and privacy, the shape of these "letterboxes" has been updated several times.
How the formats evolved
Four main address formats work in parallel on the Bitcoin network today. They are fully compatible: you can send coins from any type to any other type. The terms of that transaction still differ a lot.
In chronological order:
- 2009: Legacy (P2PKH) – addresses start with 1
- 2012: Nested SegWit (P2SH) – addresses start with 3
- 2017: Native SegWit (Bech32) – addresses start with bc1q
- 2021: Taproot (Bech32m) – addresses start with bc1p
Each generation has its own job.
Legacy addresses (P2PKH): the historical default
- Start: always the digit 1
- Example: 1A1zP1eP5QGefi2DMPTfTL5SLmv7DivfNa (the first address in history, created by Satoshi Nakamoto)
- Case: case-sensitive (upper and lower case mean different things)
- Script: Pay-to-Public-Key-Hash
This is the original format, set by the network's creator in 2009. In the early years it was the only standard.
How it works. In Legacy the sender's digital signature, the proof of the right to move the coins, is packed directly into the transaction body.
The drawback today is wasteful use of block space. A Bitcoin block is historically capped at one megabyte. Cryptographic signatures take the lion's share of the data, up to 65% of the whole transaction, so transfers from old Legacy addresses are the heaviest in bytes.
In practice. Addresses that start with 1 are obsolete. Every service in the world still accepts them, but sending from such an address costs the highest possible network fee. Use Legacy only when you have to, for example when you withdraw from an old service that has not updated its software in the last eight years.
Nested SegWit (P2SH): a compatibility bridge
- Start: always the digit 3
- Example: 3J98t1WpEZ73CNmQviecrnyiWrnqRhWNLy
- Case: case-sensitive (Base58)
- Script: Pay-to-Script-Hash
P2SH appeared in 2012 to support complex setups, for example multi-signature accounts, where several owners must agree before a transfer goes out.
Addresses that start with 3 became important in 2017, when Segregated Witness (SegWit) was deployed. SegWit's job was to separate the heavy digital signatures from the base transaction data and move them into their own structure, which lightens the network and cuts the cost.
So that the upgrade would not break conservative services, developers wrapped SegWit inside the already proven P2SH format.
How it works. To old nodes the address looks like a familiar script address starting with 3, but inside it uses SegWit. That cut the actual weight of transactions and lowered network fees by about 20–30% compared with classic Legacy addresses.
In practice. A reliable universal option. If an external platform says it cannot yet send coins to the newer generation of addresses, an address starting with 3 is the compromise.
Native SegWit (Bech32): the everyday standard
- Start: always the prefix bc1q
- Example: bc1qar0srrr7xfkvy5l643lydnw9re59gtzzwf5mdq
- Case: lowercase only (you cannot get the case wrong)
- Script: Pay-to-Witness-Public-Key-Hash (P2WPKH)
Native SegWit (Bech32) is SegWit in its pure form, without an intermediate container or a software wrapper.
The designers spent particular attention on comfort and on protection from human error:
- The largest saving on fees. Transactions from bc1q addresses weigh the fewest virtual bytes (vBytes). Compared with Legacy, the fee to send drops by 40–50%. When the mempool is crowded, that gap is real money.
- No case confusion. Older addresses use Base58, where a capital O is easy to mix with the digit 0, and a capital I with a lowercase l. Bech32 is strictly lowercase, and lookalike characters are removed from the alphabet.
- Built-in error detection. Bech32 carries a checksum. If you mistype up to four characters, the wallet sees the distortion and blocks the send, so the funds stay put.
In practice. Native SegWit (bc1q) is the best choice for everyday transfers on Quantum and in a personal non-custodial wallet. It gives the lowest fees and the strongest resistance to a technical slip.
Taproot (Bech32m): where the network is going
- Start: always the prefix bc1p
- Example: bc1p0xlxvlhemja6c4dqv22uapctqupfhlxm9h8z3k2e72q4k9hcz7vqzk5jj0
- Case: lowercase only
- Script: Pay-to-Taproot (P2TR)
In November 2021 Bitcoin activated Taproot. It brought Schnorr signatures and Merkle trees (MAST) into the network.
What Taproot changed:
- Privacy for complex operations. Multi-user wallets, Lightning Network channels and complex smart contracts look on-chain exactly like an ordinary one-person transaction. An outside observer cannot see the inner logic of the transfer.
- Efficiency of complex transfers. For a simple send the saving is comparable to Native SegWit, but when a transaction has dozens of inputs and signatures the data shrinks further.
- A base for new tools. Taproot's design opened the way for Ordinals and BRC-20 tokens, by letting digital data be attached to individual satoshis.
In practice. The most advanced standard today. Most current non-custodial wallets already support bc1p addresses. It suits people who actively use the newer parts of the network.
A quick comparison
Four profiles are enough to choose an address:
- Legacy (1...): fee saving 0% (the expensive baseline). Error protection is basic. Supported by 100% of services worldwide.
- Nested SegWit (3...): fee saving about 20–30%. Error protection is basic. Supported by 99% of services.
- Native SegWit (bc1q...): fee saving 40–50%. Error protection is a mathematical checksum. Supported by more than 95% of platforms.
- Taproot (bc1p...): fee saving up to 50–55% on complex transactions. Stronger protection and the most privacy for the conditions of the transfer. Support across the network is still growing.
Can you reuse a Bitcoin address?
This is one of the most common questions. You copied a wallet address a month ago, saved it in a phone note, and now you want to send a new transfer there without generating a fresh address.
The direct technical answer: yes. The Bitcoin blockchain will accept a repeat payment. The funds will not vanish, and they will show on your balance.
From the point of view of security, financial privacy and the way Bitcoin is built, address reuse is strongly discouraged.
The reason sits in the difference between an account balance and the UTXO model.
Account balances versus UTXO
In a traditional bank, or on a chain such as Ethereum, the balance belongs to one account. If the account holds $1000 and someone sends another $200, the single line becomes $1200.
Bitcoin works differently, on unspent transaction outputs (UTXO).
Inside the blockchain bitcoins are not one lump sum. They exist as indivisible digital cheques, or notes, of different denominations:
- Suppose the wallet holds a digital note of exactly 1 BTC.
- You want to send a counterparty 0.15 BTC.
- The protocol cannot cut a piece off that note. It takes the whole 1 BTC, destroys it as an input, and creates two new outputs.
- The first output, 0.15 BTC, goes to the recipient.
- The second output, 0.85 BTC minus the miner fee, comes back to you on a purpose-made change address.
That is why a modern wallet is not one account number. It is a large tree of addresses controlled by a single master phrase.
Why reusing one address is a bad idea
There are two solid reasons to avoid regular transfers to the same address.
Your financial history becomes one open book
Bitcoin's public ledger is fully transparent. Every transaction stays there permanently.
If you use the same address for incoming transfers, withdrawals from an exchange and transfers to people you know:
- Any counterparty you sent even a modest amount can open a public block explorer and see your whole ledger in one click: the current balance, when funds arrived and from whom, and which addresses they left for.
- Analytics services cluster repeated addresses. Matching those chains with digital traces (IP addresses, website verifications, online purchases), they can assemble a full financial profile of the owner.
A new address for each new transfer breaks the direct link. An outsider cannot tell which part of the transaction went to the counterparty and which part stayed with you as change.
The public key is revealed
While an address is only used to receive coins, the network sees nothing but its cryptographic hash, a protective fingerprint. The real public key stays hidden.
The moment you make an outgoing transaction from that address, you have to show the network your public key and a digital signature, to prove the right to move the coins.
If coins remain on that address after the send, or you receive to it again later, the cryptographic cover is thinner: the public key is already public. As computing power grows, including quantum computing, addresses whose public keys have been published are potentially more exposed than addresses whose keys have never appeared on the network.
How modern HD wallets work
In 2013 the industry stopped asking people to track addresses by hand and adopted hierarchical deterministic wallets (HD wallets). Reliable hardware and mobile wallets are built on this standard.
The principle is simple:
- All of your addresses are derived mathematically from one root, your secret seed phrase of 12 or 24 words.
- Each time you tap Receive, the app generates the next unused address from an endless chain.
- When you send, the wallet creates a temporary change address on its own and returns the unspent remainder there without asking you to manage it.
Old addresses never stop working. If someone sends funds by mistake to an address you used three years ago, the coins are not lost: the wallet finds them on the blockchain and adds them to the total balance.
The basic hygiene rule is: one incoming transaction, one address.
Clipboard safety
Knowing the formats will not protect the capital if you skip basic protection from malware.
- Watch for clipper viruses. The most common malware for stealing cryptocurrency quietly watches your device clipboard. The moment you copy a Bitcoin address, it swaps in a hacker's address with similar first and last characters.
- Always check the control characters. Never press send blind. Compare the first 5–6 and the last 5–6 characters in the confirmation window with the address in the original source.
- Prefer QR codes. Scanning a graphic code with a camera removes the risk of the operating system's clipboard being intercepted.
The main points
Bitcoin address formats have moved toward faster, cheaper and safer transfers:
- Addresses starting with 1 (Legacy) are history. Use them only when there is no other option.
- Addresses starting with 3 (Nested SegWit) are the universal compatibility bridge.
- Addresses starting with bc1q (Native SegWit) are the everyday choice and can cut the fee by up to half.
- Addresses starting with bc1p (Taproot) give the strongest privacy and the newest design.
- Reusing an address is technically allowed and still a bad idea: for privacy, receive each transfer on a newly generated address.
The step-by-step withdrawal from the exchange to your own wallet is in How to withdraw crypto from Quantum to your wallet.
Common questions
What is a Bitcoin wallet address?
A Bitcoin wallet address is a public identifier for an incoming transfer, not a permanent account number. The prefix shows the generation: 1, 3, bc1q or bc1p. That generation sets how much of the block the transaction occupies and what network fee you pay.
An address starts with bc1. Which format is it?
If an address starts with bc1, look at the next character. bc1q is Native SegWit (Bech32). bc1p is Taproot (Bech32m). Both are lowercase only, and the wallet can catch a typo before the send.
What is the difference between a Bitcoin address starting with 1 or 3?
A Bitcoin address starting with 1 or 3 is one of the two older formats. 1 is Legacy: the heaviest transaction and the highest network fee. 3 is nested SegWit: to old services it looks familiar, and the transfer already weighs about 20–30% less than Legacy.
Can you reuse an address?
You can. The network will accept the transfer and the coins will not disappear. For privacy it is a bad habit. The same address stitches the whole history of incoming transfers together, and after the first outgoing transaction the public key stays on the blockchain. A new incoming transfer is better received on a new address.
Are Bitcoin address formats compatible?
Bitcoin address formats are compatible: you can send from any type to any other type. What changes is the data weight, the fee and the resistance to a typo, not whether the transfer can arrive. For ordinary transfers bc1q is the convenient choice. If a platform does not accept it yet, an address starting with 3 is the working fallback.
If you do not have an exchange account yet, register and see which address the exchange gives you for an incoming transfer.
Digital tokens (also called tokens) are not a means of payment and are not backed by the state. Acquiring tokens may lead to the complete loss of funds and other civil-law assets transferred in exchange for tokens (including as a result of token price volatility, technical failures and/or errors, and unlawful actions, including theft).