Skip to content
INTERN STATUS

Wallet basics

What Is a Bitcoin Address? (And Why It Isn't an Account)

What a Bitcoin address is, what the 1, 3, bc1q and bc1p prefixes mean, why you should not reuse one, and what to check before you send bitcoin.

By SATOSHI'S INTERN Editorial DeskPublished 8 MIN READFacts checked

Part of What Is a Crypto Wallet? Keys, Not Coins

A Bitcoin address is a short string, such as one starting with 1, 3, bc1q or bc1p, that tells a sender's wallet how to lock coins so that only you can spend them later. It is derived from a public key or a script, so it is safe to share, much like an email address. It is not an account, it does not hold a balance, and it is never a password, private key or seed phrase.

An address is not an account

A bank account is a box with a number in it. The Bitcoin ledger has no boxes. It records individual chunks of bitcoin, called unspent transaction outputs, and each chunk carries a small locking condition along the lines of "spendable by whoever can sign for this key". An address is a compact way of writing that condition down. The Bitcoin Wiki puts it plainly: addresses "are not wallets nor accounts, and do not carry balances."

Your wallet holds the keys, finds the outputs it can unlock, and shows you their total.

That design has a practical upside. One wallet can have thousands of addresses, all derived from the same seed phrase, and good wallets hand you a new one each time you tap Receive. The step-by-step maths of how a key becomes an address is in the wallet guide.

Bitcoin address formats: 1, 3, bc1q and bc1p

Bitcoin has picked up several address types over the years. The first characters tell you which one you are looking at.

Table: Bitcoin mainnet address formats

PrefixNameOutput typeSpec and encoding
1LegacyP2PKH (pay to public key hash)Original software; Base58Check, version byte 0
3Script hashP2SH: the hash of a script, e.g. multisig or escrow, or SegWit nested in P2SHBIP-13; Base58Check, version byte 5
bc1qNative SegWitWitness v0: P2WPKH (20-byte) or P2WSH (32-byte program)BIP-141, BIP-173; Bech32
bc1pTaprootWitness v1: P2TR (32-byte key)BIP-341, BIP-350; Bech32m

The Bitcoin Wiki uses 1BvBMSEYstWetqTFn5Au4m4GFg7xJaNVN2 as a legacy example and 3J98t1WpEZ73CNmQviecrnyiWrnqRhWNLy for P2SH. BIP-173 gives bc1qw508d6qejxtdg4y5r3zarvary0c5xw7kv8f3t4 (42 characters) as a native SegWit example, and BIP-350's test vectors include bc1p0xlxvlhemja6c4dqv22uapctqupfhlxm9h8z3k2e72q4k9hcz7vqzk5jj0 (62 characters) for Taproot. Do not send anything to these; they are illustrations.

Why bc1q and bc1p

In the newer formats, bc means mainnet and 1 is a separator. The next character encodes the SegWit version: q for version 0, p for version 1. That is why every native SegWit address you see starts bc1q and every Taproot address starts bc1p.

Taproot needed a new checksum. BIP-350 explains that the original Bech32 had a flaw: if the final character is a p, inserting or deleting q characters just before it does not invalidate the checksum. Bech32m fixes that, and it is used for version 1 and later.

Taproot itself, in BIP-341's words, is "a new SegWit version 1 output type, with spending rules based on Taproot, Schnorr signatures, and Merkle branches". BIP-341 records that the deployment activated at height 709,632 on mainnet; that block's timestamp is 14 November 2021, 05:15 UTC.

Does the format matter?

To receive, mostly no: any address your wallet gives you is valid. The formats differ in fees and features. SegWit (BIP-141) counts witness data, where signatures live, at a quarter of the weight of other transaction data, so spending from bc1q and bc1p outputs usually needs less block space than spending from legacy ones. Taproot key-path spends also reveal less about how a coin could have been spent.

To send, check that your wallet or exchange supports the format it is being asked to pay. If a service rejects a bc1 address you know is valid, one possible cause is that the service does not support that format yet. Ask it, rather than assuming the address is wrong.

Testnet addresses, used for coins with no value, use the prefix tb1 for SegWit. If a payment request for real bitcoin shows one, stop and ask why.

Checksums catch typos, not scams

Every address format includes a checksum. For the older Base58 addresses, the Bitcoin Wiki puts the chance of a mistyped address being accepted as valid at 1 in 2^32, about 1 in 4.29 billion. Base58Check also leaves out the characters 0, O, I and l, so they cannot be confused.

Bech32 guarantees detection of any error affecting at most four characters. Its addresses can be written all lower-case or all upper-case (encoders output lower case, and mixed case is rejected), which makes them easier to read aloud.

None of this helps with a perfectly valid address that belongs to someone else, which is exactly what clipboard malware and address-poisoning scams give you.

Is it safe to share or reuse a Bitcoin address?

Sharing is safe in the sense that nobody can spend from an address by knowing it. The cost is privacy. Every transaction to and from an address is public and permanent. Bitcoin is pseudonymous: your name is not on the address, but once an address is linked to you, by an exchange, an invoice, a public post, its whole history is linked too.

Reuse makes that worse. bitcoin.org's privacy guidance is direct: "You should use a new Bitcoin address each time you receive a new payment." It adds that "something not traceable currently may become trivial to trace in the future." The Bitcoin developer guide notes that using each public key only twice, once to receive and once to spend, gives "a significant amount of financial privacy".

The Bitcoin Wiki gives a second reason for fresh addresses: if a merchant uses one address for everyone, anyone who sees a payment arrive can falsely claim they made it.

HD wallets make this free. New addresses come from the same seed phrase, so there is nothing extra to back up.

Checks before you send bitcoin

  1. Get the address from the source. Copy it from the recipient's invoice or wallet, not from your transaction history, where a lookalike may have been planted.
  2. Compare the whole address after pasting, including a chunk from the middle. Clipboard malware can replace a copied address with the attacker's.
  3. Check the format matches the network. A Bitcoin mainnet address starts 1, 3 or bc1. An address starting 0x belongs to Ethereum-style networks, and any "bitcoin" there is a token, not native bitcoin. Choosing the wrong network on an exchange withdrawal can put funds somewhere hard or impossible to retrieve.
  4. On a hardware wallet, check the address on the device screen. Trezor advises checking the address on the device against the one shown in the app; when sending, "If anything doesn't match, don't approve."
  5. Send a small test first when the amount is large or the recipient is new. That is our advice, not a protocol rule: a second fee is cheaper than an irreversible mistake.
  6. Wait for confirmations on the receiving side. bitcoin.org notes new blocks are added "approximately every 10 minutes on average", and that "6 confirmations is often considered to be as safe as waiting 6 months on a credit card transaction."

Backups, phishing and the rest of the routine are in the crypto wallet security checklist.

Sources

Your address is public. Your keys are not. The Intern List only ever asks for an email, a Google login or a wallet signature.

JOIN THE INTERN LIST

Educational content, not financial, legal or tax advice. Nothing here says any asset will go up. Crypto is risky — read the Risk Disclosure.