Bitcoin addresses 1, 3, bc1q and bc1p: which to use?

Your wallet shows a Bitcoin receiving address starting with bc1q, while another app shows one starting with 1, 3 or bc1p. All four can be Bitcoin mainnet addresses. They encode different output types, though, and the sending service may not support every type. A familiar prefix by itself does not prove that an address is valid or that you control it.

For a native BTC withdrawal, use an address generated by the receiving wallet for Bitcoin mainnet, then check whether the sender accepts that format. Picnic validates all four mainnet groups when the complete address is valid and, for bc1, lowercase. That does not mean an address on another network will work, or that every holding with “BTC” in its name can be withdrawn as native bitcoin.

What do 1, 3, bc1q and bc1p Bitcoin addresses mean?

Trezor's address guide describes the four common patterns and uses bc1q by default for its SegWit wallet. BIP 350 defines Bech32m checksums for version-one witness addresses such as Taproot. Both were checked on November 9, 2026.

These are not four separate networks. A Bitcoin wallet generating bc1q and one generating 1 receive coins on the same mainnet. Transfers between address types are generally possible; the restriction you may meet is often the sender's software or address validator. If a sender rejects bc1p, do not edit the characters or choose a different network. Generate another address type in the receiving wallet that the wallet actually controls and the sender supports, if the wallet offers one.

Is bc1q better than bc1p? Which address has lower fees?

bc1q is often the straightforward compatibility choice when you have no reason to use Taproot. bc1p enables Taproot features, but some sending services may still reject it. 1 and 3 remain valid when produced by a trustworthy wallet. The goal is not to select the “newest” prefix in isolation: select your wallet's address that the sender can use.

A Bitcoin network fee is not a fixed price attached to a prefix. It depends on block-space demand and the virtual size of the whole transaction: the inputs spent, how they are signed, the outputs created and the fee rate. SegWit formats can reduce the weight of certain spends compared with Legacy. It does not follow that every withdrawal to bc1p costs less than one to bc1q.

There is a subtle difference between the receiving address and the transaction's spent inputs. Your address type affects the output created now; much of today's sending cost comes from the inputs the wallet or service spends. An exchange may also charge its own withdrawal fee separately from the network fee. Bitcoin.org explains variable transaction fees. Compare the BTC amount leaving, the quoted fee and the expected net receipt on the actual confirmation screen rather than relying on a generic fee table. Our crypto withdrawal cost guide (in Portuguese) explains the layers.

Which Bitcoin addresses can receive a Picnic native BTC withdrawal?

As checked in Picnic's product code on November 9, 2026, its destination validator accepts valid Bitcoin mainnet addresses in the 1, 3, bc1q and bc1p groups. It checks structure and checksum, not just the prefix. bc1 addresses must be lowercase: Picnic rejects the equivalent all-uppercase form (BC1Q… or BC1P…). A tb1 test-network address (testnet or signet) or an EVM 0x address is not a native Bitcoin destination in this flow.

The source holding matters as much as the destination. At this date, the native BTC withdrawal route supports WBTC on Polygon, Optimism, Arbitrum and Ethereum. WBTC on Gnosis and cbBTC on Base are not in that route. The technical source minimum is 3,000 WBTC base units, equivalent to 3,000 sats, under the product rule checked on this date. A quote still needs an available route and a usable BTC amount at the destination. The minimum reflects route and Bitcoin network costs; it is not a promised fixed platform fee.

This route converts the source token to native BTC on Bitcoin. It is not a direct WBTC transfer to a bc1 address. WBTC and native BTC are different assets (Portuguese guide). A 0x destination belongs to an EVM network and another flow. Lightning also requires explicit support; it is not interchangeable with an on-chain Bitcoin address.

How do you verify a Bitcoin address before sending?

1. Open the receiving wallet. Choose Bitcoin mainnet and use the wallet's own Receive action. Do not copy a purported support agent's address from a message.
2. Match asset and network at both ends. The destination must receive native BTC on Bitcoin; confirm that the send actually ends as native BTC, not WBTC or another token.
3. Paste and compare the full address. A matching prefix and last few characters do not rule out clipboard malware. With a hardware wallet, verify the address on the device screen too.
4. Review the financial details. Check the minimum, quoted charge, net BTC and any conversion between the source token and the destination. Do not switch networks merely to force a missing quote.
5. Consider a small test. If the sender imposes a withdrawal minimum, the test must exceed it and make sense after fees. Wait for confirmation and wallet credit before moving the remainder. A test limits the impact of a mistake, but it does not make the transfer reversible.

Bitcoin.org recommends checking the entire address and considering a test. Once a Bitcoin transaction to the wrong address is confirmed, support cannot cancel it. If you are moving BTC from an exchange, our exchange withdrawal walkthrough (Portuguese) covers the full sequence.

What if the sender rejects the address?

First, check that your receiving wallet generated a Bitcoin mainnet address. tb1 denotes a Bitcoin test network such as testnet or signet; 0x is an address on another family of networks. Copy again from the wallet without spaces or edits. If the wallet supplied an all-uppercase address (BC1Q… or BC1P…), use its equivalent lowercase form for Picnic and verify the entire address. This does not apply to 1 or 3 addresses; if a Bech32 address mixes uppercase and lowercase, do not try to repair it: copy it again from the wallet. A rejected bc1p may mean the sender does not support Taproot. If the receiving wallet allows it, generate a fresh bc1q address there and verify it on the device. Never try to “convert” an address by changing its prefix.

If the address passes validation but no withdrawal quote appears, examine the source asset, minimum, route availability and service state too. The destination format may not be the problem. If funds were already sent, save the transaction ID and inspect a Bitcoin explorer; do not send another payment to “unlock” the first. If you actually chose a different network, read our wrong-network guide (Portuguese) without assuming recovery is possible.

The short answer: 1, 3, bc1q and bc1p can all receive native BTC. Use an address generated by your wallet, confirm sender compatibility, review the net amount and verify the entire string. For Picnic, also check that the WBTC holding is on a supported source network. Control of the destination matters more than the appearance of the prefix.

Picnic is a technology platform that lets users independently interact with USDC, a U.S. dollar-pegged stablecoin issued by Circle, on public blockchains. USDC is not legal tender in Brazil.

Displayed exchange rates vary with market conditions. The final applicable amount is the one shown on the transaction confirmation screen. Cryptoassets involve risks, including volatility and loss of peg.

Picnic does not custody user assets and is neither a financial institution nor a virtual asset service provider. Sending and receiving U.S. dollar payments through a U.S. account is offered in partnership with Noah Savings Inc. Terms and conditions apply.

Information verified in November 2026.