Definition: Bitcoin address formats are human-readable encodings of payment destinations that wallets convert into locking scripts on Bitcoin. The format hints at the output type, but an address is not a wallet account, a balance, a public key in every case, or a private key. 1
| Official specifications | BIP 16; BIP 141; BIP 173; BIP 341; BIP 350 |
|---|---|
| Directories | Bitcoin Directory |
What a Bitcoin address represents
An address is a compact way to share the conditions for a Bitcoin transaction output. A wallet decodes it and builds the output’s Bitcoin Script, which nodes later evaluate when someone tries to spend that output. A wallet can create many receiving addresses from its keys; the address itself does not hold coins. The spendable value is recorded in transaction outputs, which are tracked as unspent transaction outputs (UTXOs). 1
Different address strings can represent different output constructions. Some encode a hash of a public key; others encode a hash of a script or a SegWit witness program. This is why an address is not always just a public key written in another format. Its checksum can catch many typing errors, but it cannot prove that the intended recipient controls the destination or that the sender selected the right network. 2
Common Bitcoin address formats
| Output type | Typical mainnet appearance | What the format represents |
|---|---|---|
| P2PKH (legacy) | 1…, Base58Check |
A hash derived from a public key |
| P2SH | 3…, Base58Check |
A hash of a redeem script; this format can also wrap a SegWit program |
| P2WPKH (native SegWit v0) | bc1q…, Bech32 |
A 20-byte witness program tied to a public-key hash |
| P2WSH (native SegWit v0) | bc1q…, Bech32 |
A 32-byte witness program tied to a witness script |
| P2TR (Taproot, witness v1) | bc1p…, Bech32m |
A 32-byte Taproot output key; spending can use a key path or, when created, a script path |
The letter after the separator does not identify every detail of an output. Both P2WPKH and P2WSH mainnet addresses begin with bc1q; their decoded witness programs differ in length and meaning. Wallet software must decode the complete address and create the matching script. BIP 141 defines the version-zero witness programs, while BIP 173 specifies Bech32 encoding for witness addresses. 3 4
Taproot uses a version-one witness program. BIP 350 specifies Bech32m for witness versions one and later, while Bech32 remains in use for version zero. A Taproot output’s 32-byte program represents its tweaked output key; it does not reveal whether the owner also committed to an optional script tree. 5 6
Mainnet and test-network prefixes
Bitcoin’s Base58Check version bytes differ between mainnet and testnet: the commonly used P2PKH versions are 0x00 on mainnet and 0x6f on testnet; P2SH uses 0x05 and 0xc4, respectively. Native SegWit encodings use a human-readable prefix: bc for mainnet and tb for testnet. These network markers help software reject an address supplied for the wrong chain, but people should still verify the network shown in both the sending wallet and receiving service. 4 7
How to read and use an address safely
Copy the full address from the recipient’s wallet or scan its QR code, then compare the first and last characters against the recipient’s displayed address before confirming. A valid checksum only checks the encoded string’s integrity; it does not confirm the recipient, amount, or network. If a wallet reports an invalid address or an unsupported format, stop and ask the recipient for a compatible destination instead of changing characters manually. Funds sent to the wrong destination may be impossible to recover.
Wallet support also matters. Older software may not recognize newer address formats, and the recipient’s wallet must be able to spend funds sent to its addresses. P2SH can represent a script hash and is also used to wrap a SegWit program for compatibility. Native SegWit and Taproot use different witness versions and checksum rules. When a wallet offers multiple receive formats, use the one that both sides support and follow the wallet’s network and compatibility guidance.
Address-format milestones
- 2012: BIP 16 deployed pay-to-script-hash, allowing a sender to pay to a short hash while the recipient later supplies the redeem script. 2
- 2017: SegWit added witness programs, including P2WPKH and P2WSH; BIP 173 defined Bech32 for native witness addresses. 3 4
- 2021: Taproot activated as a SegWit version-one output type, and BIP 350 defined Bech32m for version-one and later witness addresses. 5 6
Common misconceptions and limits
- An address is not an account balance. Bitcoin value is tracked in transaction outputs, not stored inside the address string.
- A checksum detects many transcription errors; it does not prove that the destination belongs to the person you intend to pay.
- Addresses with the same prefix can still represent different output types. For example, both P2WPKH and P2WSH use the mainnet
bc1qprefix. - A familiar-looking prefix is not enough to verify the network. Check the wallet’s selected network and the recipient’s instructions.
- Address formats do not all offer the same wallet compatibility or spending conditions. A sender should use a format the receiving wallet supports.
Page updated: November 10, 2026.
Related Terms
Related Articles
- Why Crypto Calls It a Wallet—and What the Metaphor Hides
- How Do Crypto Bridges Work—and Why Are They Such a Hack Target?
- Bitcoin as Collateral: Bank Loans, Mortgages, and DeFi Explained
- What Happens to Bitcoin Mining Rewards After New BTC Issuance Ends?
See Also
Sources
- Bitcoin Core Developers. “Transactions.” Bitcoin Developer Guide. Accessed November 10, 2026. https://developer.bitcoin.org/reference/transactions.html.
- Andresen, Gavin. “Pay to Script Hash.” Bitcoin Improvement Proposal 16. Assigned January 3, 2012. https://github.com/bitcoin/bips/blob/master/bip-0016.mediawiki.
- Lombrozo, Eric, Johnson Lau, and Pieter Wuille. “Segregated Witness (Consensus Layer).” Bitcoin Improvement Proposal 141. Assigned December 21, 2015. https://github.com/bitcoin/bips/blob/master/bip-0141.mediawiki.
- Wuille, Pieter. “Base32 Address Format for Native v0–16 Witness Outputs.” Bitcoin Improvement Proposal 173. Accessed November 10, 2026. https://github.com/bitcoin/bips/blob/master/bip-0173.mediawiki.
- Wuille, Pieter. “Bech32m Format for v1+ Witness Addresses.” Bitcoin Improvement Proposal 350. Assigned December 16, 2020. https://github.com/bitcoin/bips/blob/master/bip-0350.mediawiki.
- Wuille, Pieter, Jonas Nick, and Anthony Towns. “Taproot: SegWit Version 1 Spending Rules.” Bitcoin Improvement Proposal 341. Assigned January 19, 2020. https://github.com/bitcoin/bips/blob/master/bip-0341.mediawiki.
- Bitcoin Core Developers. “Chain Parameters.” Bitcoin Core source code,
src/kernel/chainparams.cpp. Accessed November 10, 2026. https://github.com/bitcoin/bitcoin/blob/master/src/kernel/chainparams.cpp.