# Bitcoin P2PKH, SegWit and Taproot Addresses

Source: https://www.btcvanity.io/blog/bitcoin-p2pkh-vs-segwit-taproot

Published: 2026-11-06

Updated: 2026-11-09

![Three address families. 1...: Legacy P2PKH: generated by this tool; 3...: P2SH: a different script construction; bc1...: Native SegWit or Taproot: not generated here.](https://www.btcvanity.io/images/blog/bitcoin-p2pkh-vs-segwit-taproot-diagram-v2.webp)

Three address families. 1...: Legacy P2PKH: generated by this tool; 3...: P2SH: a different script construction; bc1...: Native SegWit or Taproot: not generated here.

[Full-size diagram (SVG)](https://www.btcvanity.io/images/blog/bitcoin-p2pkh-vs-segwit-taproot-diagram-v2.svg)

[Diagram download (PNG)](https://www.btcvanity.io/images/blog/bitcoin-p2pkh-vs-segwit-taproot-diagram-v2.png)

The current worker generates legacy P2PKH addresses. It does not generate bc1 SegWit or Taproot addresses.

## The visible prefix is a clue to the format

Bitcoin supports several address encodings. This service produces legacy P2PKH results, so a request for a bc1 pattern cannot be satisfied by changing a setting here.


| Mainnet form | Typical purpose | Generated here |
| --- | --- | --- |
| 1… | Legacy P2PKH | Yes |
| 3… | P2SH; the address alone does not reveal every spending condition | No |
| bc1q… | Native SegWit version 0 | No |
| bc1p… | Taproot version 1 | No |


## Do not edit an address into another format

Changing 1 to bc1 does not convert a destination. An address encodes particular data under particular rules. Bech32 and Bech32m also have different checksum requirements. A wallet must construct the destination correctly.

A private key can participate in different output constructions, but their addresses are not interchangeable. Importing the same secret with a different script choice can display a different address.


## Use the wallet requirement as your starting point

Confirm which address type your receiving workflow requires. If it requires native SegWit or Taproot, use a wallet or generator that explicitly supports that type. If legacy P2PKH is suitable, continue with [the Base58 pattern guide](https://www.btcvanity.io/blog/bitcoin-vanity-address-format).

The pattern itself does not reduce network fees. See [what actually affects transaction fees](https://www.btcvanity.io/blog/bitcoin-vanity-address-transaction-fees) for the distinction between appearance and transaction construction.


## Explore the related mechanism

- [Bitcoin Vanity Address Patterns: Prefix, Suffix and Base58](https://www.btcvanity.io/blog/bitcoin-vanity-address-format) — This generator returns Bitcoin mainnet legacy P2PKH addresses beginning with 1. Patterns use Base58, which excludes 0, O, I and lowercase l.
- [Do Bitcoin Vanity Addresses Change Transaction Fees?](https://www.btcvanity.io/blog/bitcoin-vanity-address-transaction-fees) — A recognizable pattern does not itself provide a transaction-fee discount. Fees depend on the transaction and spending conditions.
- [Open the complete workflow guide](https://www.btcvanity.io/guide) to place these checks in order.
- [Open the address generator](https://www.btcvanity.io/) when you have chosen a compatible format and pattern.

## Sources

- [Bitcoin developer transactions guide](https://developer.bitcoin.org/devguide/transactions.html)

- [BIP 173: Bech32 addresses](https://github.com/bitcoin/bips/blob/master/bip-0173.mediawiki)

- [BIP 350: Bech32m](https://github.com/bitcoin/bips/blob/master/bip-0350.mediawiki)



Editorial method: https://www.btcvanity.io/about#publication-method