Address format
Bitcoin P2PKH, SegWit and Taproot Addresses
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.
The pattern itself does not reduce network fees. See what actually affects transaction fees for the distinction between appearance and transaction construction.
Explore the related mechanism
- Bitcoin Vanity Address Patterns: Prefix, Suffix and Base58 — 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? — A recognizable pattern does not itself provide a transaction-fee discount. Fees depend on the transaction and spending conditions.
- Open the complete workflow guide to place these checks in order.
- Open the address generator when you have chosen a compatible format and pattern.
Sources and editorial method
The technical references below support the concepts discussed in this article. Examples and comparison worksheets are explanatory, not measured service benchmarks.
Read next
Address format3 min read
Bitcoin Vanity Address Patterns: Prefix, Suffix and Base58
Choose a valid Bitcoin vanity prefix or suffix with worked examples. Learn why P2PKH starts with 1 and why a pattern cannot turn it into bc1.
Transactions2 min read
Do Bitcoin Vanity Addresses Change Transaction Fees?
A recognizable pattern does not itself provide a transaction-fee discount. Fees depend on the transaction and spending conditions.
Wallets2 min read
Importing a Bitcoin Vanity WIF into a Wallet
The result contains a Wallet Import Format private key. Use a wallet that explicitly supports the returned key and legacy P2PKH addresses.
Address format2 min read
Bitcoin Address or Transaction ID: How to Tell Them Apart
A receiving address and a transaction identifier describe different things. The result of this generator is an address and its private key, not a transaction.