Bitcoin addresses explained: four kinds of lock, and a built-in typo check
A Bitcoin address is a short, copyable name for a lock on coins. Its first characters tell you the type: 1, 3, bc1q or bc1p. Each type carries a checksum that catches most typos, and using a fresh address for every payment keeps the public ledger from joining up your payments.
In the village notebook, nobody's name appears. Each line says something like "these 10 coins belong to whoever can open lock number 7Q3X". Anna has a drawer full of locks. Only she has the keys.
When Rosa wants to pay Anna, Anna doesn't give her a name. She gives her a lock number, written so it can be read out, copied and checked. If Rosa gets a digit wrong, the number simply doesn't work, and she has to ask again.
That lock number is a Bitcoin address. Not an account, not a name, not a place. A label for a lock, with a built-in spelling check.
What it is
A Bitcoin address is a short code that tells the sender how to lock the coins so that only the receiver can spend them. Usually it's made from a fingerprint of the receiver's public key, which comes from their private key, or from a fingerprint of a more complex spending rule.
The developer guide describes the classic kind as a string "containing an address version number, the hash, and an error-detection checksum to catch typos" (Bitcoin developer guide). The first characters tell you which kind of lock you're looking at.
How it works: one block, four kinds of address
All four of these received coins in the same block, 976,485, written on 18 November 2026 at 21:05:12 UTC.
- Starts with 1: the original. Transaction 1deddb8d sent 50,500,000 satoshis to 143J9ojX6nJ9ghoRG6T6XdMTyAzGpncZqL (mempool.space). This is pay-to-public-key-hash, which the developer guide calls "the most common form" of locking script. Upper and lower case letters mixed, which is why reading one aloud is a test of friendship.
- Starts with 3: a lock with a rulebook. Transaction 040bebcc sent 639,981 satoshis to 3AQ9Zy1PfwJyP8NUbAD75LDFheX37GyFV9 (mempool.space). BIP 13, written by Gavin Andresen in 2011, defined this type to support "arbitrarily complex transactions", such as needing two keys out of three. The address is a fingerprint of the rules, and "for the main network, byte 5 becomes the character '3'" (BIP 13).
- Starts with bc1q: lower case, stronger check. Transaction 19011ba7 sent 10,000,000 satoshis to bc1qz4g79wy8cfdgw63m6ed0pgq4apqm5sejvwaatm (mempool.space). BIP 173, by Pieter Wuille and Greg Maxwell, assigned in March 2017, introduced this bech32 format. "bc" means Bitcoin's main network, "1" is a separator, and the q marks version 0. Its authors replaced the old style partly because "The mixed case in base58 makes it inconvenient to reliably write down, type on mobile keyboards, or read out loud" (BIP 173).
- Starts with bc1p: Taproot. Transaction 34244e5e sent 5,195 satoshis to bc1pufsmts0mpvjqe572j3d8ac97sdqmc6lpsqt8l8xs5elktmp79ptqats6st (mempool.space). The p marks version 1, the Taproot upgrade that "Who controls crypto?" follows from proposal to rule. These addresses use a tweaked checksum, bech32m, defined in BIP 350 by Pieter Wuille in December 2020 (BIP 350).
The typo check
Every one of these formats ends with a checksum: a few characters calculated from the rest. Change one character and the sum no longer adds up, so a wallet refuses the address instead of sending coins to nowhere.
The newer format makes a promise the old one couldn't. BIP 173 says its checksum "guarantees detection of any error affecting at most 4 characters" (BIP 173). And when a flaw turned up, where a 'p' at the end could have extra 'q' characters added or removed without the checksum noticing, BIP 350 fixed it for the newer address versions (BIP 350). Even the spelling check got a spelling check.
Why it matters: one address, one use
Addresses are public. Anyone can look one up and see every payment to and from it, forever. That's why the developer guide says: "for both privacy and security, we encourage you to build your applications to avoid public key reuse" (Bitcoin developer guide). The Bitcoin Wiki is blunter: "Invoice addresses are not intended to be used more than once" (Bitcoin Wiki).
Look at our block again. Three of the four payments above had a second output, and in all three it went straight back to the address the coins came from. Anyone reading the ledger can tell which output was the payment, which was the change, and join those payments to everything else that address ever did.
Where people get it wrong
- "An address is my account." It's a lock label. A good wallet makes a new one for every payment, all opened by keys from the same seed.
- "The checksum protects me from scams." It catches typos. It can't tell you that a perfectly valid address belongs to a thief.
- "Different address types are different coins." They all hold the same bitcoin. Modern wallets can send to all four.
- "Reusing an address is harmless." It links your payments in public, for anyone patient enough to look.
The sting: check the whole address
Some malware watches what you copy. Kaspersky's researchers describe it as "replacing part of the clipboard contents once it detects a wallet address in it" (Kaspersky Securelist). The swapped address passes every checksum, because it's a real one. Before you confirm a payment, compare the address on screen with the one you were given: the start, the middle and the end, not just the first few characters.
The stranger at the gate doesn't need to break your wallet. He only needs you to read the first four letters and trust the rest.
Frequently asked questions
What is a Bitcoin address?
A Bitcoin address is a short code that tells a sender how to lock coins so that only the receiver can spend them. It's usually derived from the receiver's public key or from a spending rule, and it includes a checksum to catch typos.
What do Bitcoin addresses starting with 1, 3, bc1q and bc1p mean?
Addresses starting with 1 are the original pay-to-public-key-hash type. Those starting with 3 are pay-to-script-hash, defined in BIP 13. bc1q addresses use the bech32 format from BIP 173, and bc1p addresses are Taproot addresses in the bech32m format from BIP 350.
What happens if I make a typo in a Bitcoin address?
In almost all cases the wallet rejects it, because the checksum no longer matches. The bech32 format used by bc1 addresses guarantees detection of any error affecting up to four characters.
Should I reuse a Bitcoin address?
It's better not to. Every payment to an address is public, so reusing one lets anyone link your payments together. Most wallets generate a fresh address for each payment automatically.
Can I send bitcoin from a bc1 address to an address starting with 1 or 3?
Yes. All address types hold the same bitcoin, and a payment can go from one type to another, as many do in every block. Very old wallets may not recognise the newer formats, so check that yours does.
Sources
- Bitcoin developer guide, Transactions (P2PKH, addresses, key reuse)
- Gavin Andresen, BIP 13: Address format for pay-to-script-hash
- Pieter Wuille and Greg Maxwell, BIP 173: Base32 address format for native v0-16 witness outputs
- Pieter Wuille, BIP 350: Bech32m format for v1+ witness addresses
- Kaspersky Securelist, Copy-paste heist or clipboard-injector attacks on cryptousers (28 March 2023)
- Bitcoin Wiki, Invoice address
- mempool.space API, transaction 1deddb8d...22fb in block 976,485 (18 November 2026)
- mempool.space API, transaction 040bebcc...52f4 in block 976,485 (18 November 2026)
- mempool.space API, transaction 19011ba7...4b9a in block 976,485 (18 November 2026)
- mempool.space API, transaction 34244e5e...d63d in block 976,485 (18 November 2026)

