Formats, network checks, address reuse and the verification habits that prevent costly mistakes.
01Addresses are payment instructions, not identities.
02Always confirm the network and full destination.
03Use a fresh receive address when practical.
Identify format, network, checksum, and privacy implications at a glance.
An address encodes conditions
A Bitcoin address is a user-facing encoding related to a locking script. Modern formats improve error detection and efficiency, but compatibility varies across older services. <strong>Networks must match.</strong> Mainnet, testnet and other networks use distinguishable formats, yet users should still confirm the selected network. Sending another asset or using an incompatible chain can make recovery difficult or impossible.
<strong>Fresh addresses improve privacy.</strong> Reusing an address makes it easier to associate payments and balances. Hierarchical deterministic wallets generate many receive addresses from one backed-up seed, so freshness does not require a new backup every time.
Validate an address without guessing from its shape
An address beginning with bc1 usually signals a modern Bitcoin mainnet format, while older formats often begin with 1 or 3. That visual check can catch an obvious mismatch, but it is not enough. Let the wallet validate the checksum and network, then verify the full destination on a trusted display.
Do not manually edit a character or assume that a similar-looking prefix proves the address belongs to the intended recipient. For repeated receipts, provide a fresh address each time. The wallet can derive it from the same backed-up seed, so using a new address does not require a new recovery phrase.
Address freshness reduces simple public linkage, while reusing one donation or invoice address exposes its complete incoming history and current unspent outputs to anyone who looks.
How an address is made and checked
An address is a public key hash or a script hash, plus a version prefix, plus a checksum, encoded so it can be copied by hand. Legacy addresses use Base58Check, whose four-byte checksum catches almost all typos.
SegWit addresses use Bech32, an encoding designed so that any single error and most combinations of errors are detected, with a character set that avoids ambiguous letters and works in QR codes at a smaller size. Taproot uses Bech32m, a small correction to Bech32. A wallet that rejects an address is nearly always right; a wallet that accepts one only confirms it is well formed.
The formats side by side
Addresses starting with 1 are pay-to-public-key-hash, the original format, still valid, with the largest inputs. Those starting with 3 are pay-to-script-hash: the script can be a multisig or, commonly, a wrapped SegWit script that lets older senders pay a SegWit user. bc1q addresses are native SegWit, either a key hash of 42 characters or a script hash of 62.
bc1p addresses are Taproot, 62 characters, introduced in late 2021. All four coexist and any wallet can send to any of them, though a few older services still cannot send to bc1p.
Addresses and privacy
An address is not an account. Wallets generate a new one for every payment you receive, all from the same seed, precisely so that your incoming payments cannot be trivially linked on the public ledger.
Reusing an address does not risk the coins, but it ties everything sent to it together and, if the address is ever connected to your name, connects all of it to you.
Give each counterparty a fresh address, avoid posting a single 'donations' address anywhere permanent, and let the wallet manage the rest; the Bitcoin privacy guide covers what the ledger reveals beyond addresses. The address checker on this site identifies type and network without touching the chain.
Verify more than the first characters
Confirm the full address or a device-displayed summary, the intended network, and the requested payment type. Use a fresh receive address when the wallet supports it, especially for unrelated counterparties.
Address questions worth checking twice
Why do addresses start with 1, 3 or bc1?
They are different formats. Addresses beginning with 1 are legacy pay-to-public-key-hash, 3 are script addresses often used for multisig or wrapped SegWit, bc1q are native SegWit and bc1p are Taproot. All are valid; newer formats produce smaller, cheaper transactions.
Can I reuse an address?
It works, but it links every payment to the same public key and makes your history easy to follow. Modern wallets generate a fresh address for each receipt from the same seed, so reuse offers no benefit.
Which address type has the lowest fees?
Native SegWit (bc1q) and Taproot (bc1p) inputs weigh less than legacy inputs, so transactions spending from them cost less at the same fee rate. The fee depends on the sender's inputs, not on the recipient's address type.
Sources and further reading
Primary documents this guide draws on. Links open the original publisher.
- BIP 173: Bech32 address format Bitcoin Improvement Proposals
- BIP 350: Bech32m format for v1+ witness addresses Bitcoin Improvement Proposals
- BIP 341: Taproot Bitcoin Improvement Proposals
- Address Bitcoin Wiki
