BitHedge

Taproot or Native SegWit: choosing a derivation

The choice a wallet offers between bc1p and bc1q is a choice of derivation path. It changes your addresses, your fees a little, and almost nothing else — but the recovery consequences are worth understanding before you switch.

Same phrase, different branch

One BIP39 recovery phrase can derive an unlimited number of key trees. Which branch a wallet walks is set by a derivation path. BIP84 gives Native SegWit (bc1q) addresses; BIP86 gives Taproot (bc1p) addresses. Same seed, different branch, entirely different address lists.

This is why restoring a phrase into a wallet that scans only one path can show an empty balance while the coins are safe on the other. Nothing is lost — the wallet is looking in the wrong branch. Any wallet worth using lets you pick, and most scan both.

What Taproot changes

Fees: a simple Taproot spend is typically a little cheaper than the equivalent Native SegWit spend. Over a lifetime of ordinary payments this is real but modest — measured in single-digit percentages of your fee, not of your money.

Privacy: the meaningful one. Under Taproot, a plain single-signature spend and a complex multi-signature or timelocked contract can look identical on-chain, because both can be spent through a single key path. It collapses a distinction chain analysts previously got for free.

Compatibility: the cost. A minority of older services and exchanges still cannot construct a payment to bc1p. It has become rare, but if you are receiving withdrawals from an unfashionable platform it is the thing that will bite.

Which to choose

If youChoose
Receive mostly from modern wallets and major exchangesTaproot (BIP86)
Receive from an older service, or want zero frictionNative SegWit (BIP84)
Care most about on-chain privacyTaproot
Are publishing an address for other people to payNative SegWit, until you know your payers can handle bc1p

Neither choice is a mistake, and neither is permanent. Switching changes which addresses the wallet hands out next; coins already received on the other branch remain spendable, as long as the wallet still scans that branch — which BitHedge does.

The recovery caveat

Write down which type you are using alongside your phrase. Not because you will lose the coins — you will not — but because a restore that shows a zero balance is a genuinely frightening thirty seconds, and the fix is simply pointing the wallet at the right derivation. Most modern wallets check both paths automatically; assuming yours will is a worse plan than a note on the same piece of paper.

Common questions

Is Taproot better than SegWit?

Slightly, for most users: marginally lower fees on simple spends and better on-chain privacy, since a simple payment becomes indistinguishable from a complex contract spend. The trade is that a small number of older services still cannot send to bc1p addresses.

Can I switch from Native SegWit to Taproot in my wallet?

Yes. Both derive from the same recovery phrase by different paths, so switching just changes the addresses the wallet issues next. Coins on the previous path stay spendable as long as the wallet continues to scan it.

What is the difference between BIP84 and BIP86?

They are derivation-path standards. BIP84 produces Native SegWit bc1q addresses; BIP86 produces Taproot bc1p addresses. One recovery phrase can produce both, and which addresses you see depends on which path the wallet walks.

Why does my balance show zero after restoring my phrase?

Usually because the wallet is scanning a different derivation path than the one your coins are on, or because the first sync has not finished. Check the address type setting and let the initial chain scan complete before concluding anything.

BitHedge is a Bitcoin-only self-custody wallet for iPhone. Keys are generated on your device and never transmitted — no account, no KYC, no tracking. See how it works.

Keep reading