A complete beginner’s guide to Bitcoin receiving addresses, Legacy, SegWit, Taproot, QR payment requests, privacy, and safe verification.
Introduction
A Bitcoin address is one of the first things users encounter when they receive Bitcoin. It appears as a long string of letters and numbers, or as a QR code that another wallet can scan.
The address looks like an account number, but Bitcoin does not maintain bank-style accounts. Behind the address is a spending condition recorded in a transaction output. A compatible wallet knows which keys and scripts can satisfy that condition later.
This distinction matters. An address can be shared to request payment, while a private key or seed phrase must remain secret. An address may identify a destination for one payment, but it is not proof of a person’s identity and it should not normally be treated as a permanent public account.
A Bitcoin address is a human-readable encoding of information a wallet uses to build a transaction output. It tells the sender where to lock Bitcoin, not who the recipient is.
In this XTS Insights guide, we will explain how Bitcoin addresses work, why several address formats exist, how addresses relate to wallets and keys, what happens after payment, and how to avoid common mistakes.
The Short Answer: What Is a Bitcoin Address?
A Bitcoin address is a payment destination generated by a wallet. The recipient shares it with a sender, and the sender’s wallet converts it into a locking script for a new transaction output.
The recipient does not need to reveal a private key to receive funds. Later, the recipient’s wallet creates the required digital signature or other authorization data to spend the output.
On Bitcoin mainnet, common addresses begin with 1, 3, bc1q, or bc1p. These prefixes usually indicate different output and encoding formats. They do not represent different versions of Bitcoin, and a sender must use wallet software that supports the destination format.
What Does a Bitcoin Address Actually Represent?
At the protocol level, Bitcoin is transferred into transaction outputs. Each output contains an amount and a scriptPubKey: a locking condition that must be satisfied before the value can be spent.
An address is a user-friendly way to encode the data needed to construct a standard scriptPubKey. Depending on the address type, that data may be derived from a public key, a script, or a Taproot output key.
This is why describing an address as a container holding coins is only a convenient shortcut. The blockchain records unspent transaction outputs, or UTXOs, that are locked by conditions. Wallet software scans for outputs it can spend and presents their total as a balance.
Bitcoin Address vs Wallet, Public Key, and Private Key
Bitcoin Address
An address is shareable payment information. It helps the sender create the correct transaction output. Sharing an address does not normally give someone the ability to spend from it.
Bitcoin Wallet
A wallet is software or hardware that manages keys, generates receiving addresses, tracks relevant UTXOs, creates transactions, and authorizes spending. One wallet can generate many addresses.
Public Key
A public key is mathematically derived from a private key. Some address types encode a hash of a public key, while Taproot uses a tweaked output key. An address and a public key are therefore related, but they are not interchangeable.
Private Key
A private key is secret signing material. Whoever controls the required private keys can authorize spending under the relevant conditions. Never share a private key, seed phrase, or wallet recovery secret as if it were a receiving address.
How Does a Wallet Create a Bitcoin Address?
The exact process depends on the output type, but a typical single-key wallet follows a general chain from secret material to a payment destination.
The wallet securely derives a private key, often from a deterministic wallet seed.
It calculates the corresponding public key using elliptic-curve cryptography.
It transforms the public key or spending policy into the data required by a standard output type.
It encodes that data with the correct network prefix and checksum, producing a readable address.
The wallet displays the address as text and often as a QR code for a payment request.
More advanced addresses may represent a script hash, a multisignature policy, or a Taproot output key rather than a simple public-key hash. For this reason, not every Bitcoin address can be reduced to ‘a hash of one public key.’
The Main Bitcoin Address Formats
Legacy P2PKH Addresses: Starting With 1
Pay-to-Public-Key-Hash, or P2PKH, is the classic address format associated with early Bitcoin use. Mainnet P2PKH addresses generally begin with 1 and use Base58Check encoding.
Legacy addresses remain valid, but spending from their outputs is usually less block-space-efficient than spending from modern SegWit outputs. Many wallets continue to support them for compatibility.
P2SH Addresses: Starting With 3
Pay-to-Script-Hash, or P2SH, addresses generally begin with 3 on mainnet. They encode the hash of a redeem script rather than a single public-key hash.
P2SH made it easier to pay complex conditions without requiring the sender to know the full script. It has also been widely used for wrapped SegWit outputs, which allowed older systems to interact with SegWit-compatible recipients.
Native SegWit Addresses: Starting With bc1q
Native SegWit version 0 addresses usually begin with bc1q on mainnet. They use the Bech32 format defined in BIP173 and commonly represent P2WPKH or P2WSH outputs.
Bech32 was designed for better error detection, efficient QR encoding, and easier handling than mixed-case Base58 strings. Native SegWit spending can also use block space more efficiently, which may reduce fees compared with equivalent legacy spending patterns.
Taproot Addresses: Starting With bc1p
Taproot uses SegWit version 1 outputs. Mainnet Taproot addresses generally begin with bc1p and use Bech32m, the checksum format specified in BIP350 for witness version 1 and later.
Taproot outputs can support a key-path spend and optional script paths. Wallet support has improved significantly, but users should still confirm that the sending service accepts bc1p addresses before relying on one.
Why Do Addresses Have Prefixes and Checksums?
Network and Format Information
Prefixes help software interpret the destination. On mainnet, familiar forms include 1, 3, bc1q, and bc1p. Test networks use different prefixes, such as tb1 for Bitcoin testnet. A testnet address is not a mainnet destination.
Checksums
Address encodings include checksums so wallets can detect many typing and transcription errors. A malformed address will often be rejected before a transaction is created.
A checksum is not an identity check. Clipboard malware can replace a correct address with a different address that is also valid. The wallet can confirm that the replacement is structurally valid, but it cannot know that the attacker is not the intended recipient.
Uppercase and Lowercase
Base58 addresses are case-sensitive. Bech32 and Bech32m strings may be encoded entirely in lowercase or entirely in uppercase, but a mixed-case string is invalid. Most wallets display them in lowercase. Users should copy or scan addresses rather than retyping them.
How Does a Bitcoin Payment Reach an Address?
The recipient asks the wallet to generate a fresh receiving address.
The recipient shares the address or a payment QR code through a trusted channel.
The sender’s wallet validates the format and converts it into the corresponding output script.
The sender reviews the destination, amount, network, and fee, then authorizes the transaction.
The transaction is broadcast. Bitcoin nodes verify it, and miners may include it in a block.
The recipient’s wallet detects the new UTXO and updates the payment status as confirmations accumulate.
The blockchain does not send a message to a named account. It records a new output with a spending condition. The recipient’s wallet recognizes that it has the keys or policy needed to satisfy that condition.
Bitcoin Addresses, QR Codes, and Payment URIs
A QR code may contain only an address, but it can also contain a structured bitcoin: payment request. BIP321 describes a modern URI format that can include an on-chain address and optional information such as an amount, label, message, or alternative payment instruction.
A QR code is simply an encoding method. Scanning it does not prove that the destination belongs to the expected person. A wallet should display the decoded payment details and require the user to review and authorize the payment.
Treat a payment request as an instruction to review, not an instruction to approve automatically.
Why Address Reuse Matters
An on-chain address can technically receive more than one payment, but routine reuse weakens privacy. Because the blockchain is public, repeated payments to the same address are easily linked. Observers may combine that history with exchange records, invoices, social posts, or other information.
Modern deterministic wallets can generate many receiving addresses from one backup, so using a fresh address for each payment does not require a new seed phrase. The wallet tracks all derived addresses as part of the same wallet.
Address reuse may still occur for public donation pages or operational reasons, but it should be a deliberate privacy trade-off rather than the default assumption.
What Is a Bitcoin Change Address?
Bitcoin transactions spend existing UTXOs in full. If the selected inputs exceed the payment and fee, the wallet normally creates another output returning the remainder to a change address controlled by the sender.
The change address is usually generated automatically. It may be unfamiliar even though it belongs to the sender’s wallet. Confusing change with a second payment is a common mistake when reading a block explorer.
Reliable backups and compatible wallet recovery are important because a wallet may use many receiving and change addresses over time.
How to Verify a Bitcoin Address Safely
Confirm that the destination is for Bitcoin on-chain and for the intended network, not another asset or a Lightning invoice.
Obtain the address through a trusted channel. For important payments, confirm it through a second independent channel.
Check the full address or use the wallet’s verification screen. Do not compare only the first and last few characters.
If using a hardware wallet, verify the receiving or sending details on the device’s trusted display when supported.
Review the amount and fee separately. A correct address does not protect against entering the wrong amount.
For a high-value or unfamiliar workflow, consider a small test transaction and confirm receipt before sending the balance.
Bitcoin payments are generally irreversible once confirmed. Operational checks matter because valid-looking mistakes cannot be corrected by a central support desk.
Common Bitcoin Address Mistakes
Sending to an address for the wrong network or a different digital asset.
Copying an address from transaction history without verifying the current recipient.
Checking only a short prefix and suffix, which can be exploited by address-poisoning or clipboard attacks.
Assuming every wallet or exchange supports a newer bc1p Taproot address.
Publishing and reusing one address without considering the privacy consequences.
Confusing an on-chain address with a Lightning invoice or other payment instruction.
Sharing a private key or seed phrase when someone asks for a receiving address.
Assuming a checksum proves the recipient’s identity rather than only the string’s structural validity.
Common Misconceptions About Bitcoin Addresses
‘A Bitcoin Address Stores Bitcoin.’
Not literally. The blockchain stores transaction outputs with spending conditions. Wallets identify the outputs they can spend and summarize them as a balance.
‘One Wallet Has Only One Address.’
Modern wallets normally generate many receiving and change addresses from one deterministic key structure.
‘An Address Reveals the Private Key.’
No. Receiving information is designed to be shared. The private key remains secret. However, revealing or reusing addresses can expose transaction relationships and balances.
‘A Valid Address Must Belong to the Intended Person.’
No. Validity only means the string passes the format’s rules. Identity must be verified through the payment context and a trusted communication channel.
‘Bitcoin Addresses Always Expire.’
A standard on-chain address does not normally expire at the protocol level. A merchant’s invoice or payment request may expire operationally, and using a fresh address is still recommended for privacy and accounting.
XTS Perspective
At XTS, we view a Bitcoin address as the meeting point between cryptography and everyday usability. It turns a complex spending condition into information a person can copy, scan, and verify.
Good education must also explain what the address does not provide. It does not identify the recipient, reverse a mistaken payment, protect a compromised clipboard, or replace secure key management.
As Bitcoin has evolved, address formats have evolved with it. Legacy, P2SH, native SegWit, and Taproot addresses reflect different output designs and encoding standards. Understanding those differences helps users choose compatible tools, interpret transactions, protect privacy, and verify payments with greater confidence.
Frequently Asked Questions (FAQ)
What Is a Bitcoin Address in Simple Terms?
It is shareable payment information generated by a Bitcoin wallet. A sender uses it to create an output that the recipient’s wallet can later spend.
How Many Characters Are in a Bitcoin Address?
There is no single length. Base58, Bech32, and Bech32m formats have different structures, and even witness addresses can vary by output type. Validate the complete string with compatible wallet software.
Can I Use the Same Bitcoin Address More Than Once?
It can remain valid, but repeated use makes transactions easier to link. A fresh receiving address is normally better for privacy and accounting.
Can Someone Steal Bitcoin With Only My Address?
An address alone does not normally authorize spending. The required private keys or script conditions are needed. Public addresses can still reveal financial activity and enable targeted scams.
Why Does My Bitcoin Address Keep Changing?
Many wallets generate a new receiving address after use. The old address may still be controlled by the wallet, while the new one helps reduce address reuse.
What Happens If I Send to the Wrong Bitcoin Address?
If the transaction is valid and confirmed, there is no central reversal. Only the controller of the destination can return the funds. Verify before sending.
Which Bitcoin Address Type Is Best?
There is no universal answer. Native SegWit is widely supported and efficient; Taproot adds newer capabilities; legacy formats may be needed for compatibility. Use a format supported by both wallets and appropriate for the spending policy.
Is a bc1 Address Always Taproot?
No. Mainnet native SegWit version 0 addresses usually begin with bc1q, while Taproot addresses generally begin with bc1p.
Can a Bitcoin Address Be Traced?
The blockchain publicly records transactions. An address is pseudonymous, but activity can be analyzed and sometimes linked to a person through external information.
Is a QR Code Safer Than Copying an Address?
It reduces typing errors, but it does not authenticate the recipient. Review the decoded address, amount, network, and payment context before approval.
Conclusion
A Bitcoin address is a readable payment destination that helps wallet software create a standard transaction output. It is connected to keys and scripts, but it is not a private key, a wallet, a personal identity, or a bank account.
Different prefixes reflect different formats: legacy P2PKH, P2SH, native SegWit, and Taproot. Their encodings include network information and checksums, yet those protections cannot confirm who owns a valid destination.
The safest practice is to use compatible wallet software, generate fresh receiving addresses, verify complete payment details through trusted channels, and keep all private keys and recovery information secret.
Key Takeaways
A Bitcoin address is shareable payment information, not secret signing material.
Wallets create transaction outputs that lock Bitcoin to conditions represented by addresses.
Common mainnet prefixes include 1, 3, bc1q, and bc1p.
Legacy and P2SH use Base58Check; native SegWit uses Bech32; Taproot uses Bech32m.
Checksums detect many mistakes but cannot identify the intended recipient.
A wallet can generate many receiving and change addresses from one backup.
Using a fresh address for each on-chain payment generally improves privacy.
Always verify the network, full destination, amount, and fee before sending.
Never share a private key or seed phrase as a receiving address.
Leave a Reply