/* No-JS mode: modules render live with the static noscript unit above */ .ba-ad:not(.ba-ad--live) { background: var(--ba-bg-block); border: var(--ba-border-strong); box-shadow: var(--ba-shadow-block); padding: 24px 60px; margin-top: 0; } .ba-ad:not(.ba-ad--live) .ba-ad__label { display: block; } .ba-ad:not(.ba-ad--live) .ba-ad__grid { max-height: none; overflow: visible; } @media (max-width: 768px) { .ba-ad:not(.ba-ad--live) { padding: 18px 24px; } } @media (max-width: 480px) { .ba-ad:not(.ba-ad--live) { padding: 16px 18px; } }

July 3, 2024

BIP84 vs BIP44: Which Derivation Path Creates the Right Address for On-Chain Transactions?

A Bitcoin wallet generating an address feels like one interchangeable process — any valid address should work the same. The derivation path determines the address format, and the format has a measurable effect on transaction fees. BIP44 generates legacy addresses starting with "1"; BIP84 generates Native SegWit addresses starting with "bc1q." Native SegWit uses a more efficient data structure, takes up less block space, and costs less to send from at any given fee rate. Bitok Arena's analysis of Bitcoin wallet configuration identifies BIP84 as the correct derivation path for minimizing fees on any on-chain transaction — a one-time check that saves on every subsequent send.

Bitok Arena Says

Two valid addresses, two derivation paths, two different fees for sending the exact same amount. The difference is not cosmetic — it is data structure. A bc1q address costs less to send from than a legacy "1" address, every time, at any fee rate, for no reason beyond which derivation path generated it. The path is set when the wallet is created.

Legacy addresses are not broken or unsafe — BIP44 remains fully functional, and older wallets sometimes default to it for compatibility. The choice of derivation path carries a direct, checkable cost implication for every transaction sent from the wrong default, indefinitely. That is the practical reason confirming BIP84 once, before the first send from a new wallet, is worth the few seconds it takes.

What Each Path Produces

BIP44, published in 2014, organized the hierarchical deterministic wallet key tree by purpose, coin type, and account. BIP84, defined after SegWit activated in 2017, applied the same structure to the Native SegWit address format. Both produce fully valid Bitcoin addresses from the same seed phrase. Only one produces the lower-fee format.

Bitok Arena Research

Bitok Arena reviewed the practical difference between BIP44 and BIP84 derivation paths for regular on-chain Bitcoin transaction fees.

BIP44 (Legacy P2PKH) — addresses starting with "1"; original Bitcoin format; larger transaction data sizes; higher fees at equivalent sat/vbyte rates; fully valid and supported.

BIP84 (Native SegWit P2WPKH) — addresses starting with "bc1q"; efficient SegWit data structure; smaller transaction sizes; lower fees at equivalent rates; default in most modern wallets.

Fee difference — a Native SegWit transaction is typically 30–40% smaller than the equivalent legacy transaction, producing proportionally lower fees at any fee rate.

Most actively maintained wallets default to BIP84. Older hardware wallet firmware, legacy-focused software wallets, and some exchange withdrawal interfaces may still default to BIP44. The address prefix is the fastest check: bc1q confirms Native SegWit; a "1" prefix confirms legacy. That check takes three seconds and is the basis for the comparison the article title asks about.

Bitok Arena Compares

BIP44 (Legacy)

✗Addresses start with "1" — original pay-to-public-key-hash format

✗Larger transaction data size — more block space per transaction

✗Higher fees at any given sat/vbyte rate due to larger transaction size

✗Default in older wallets and some exchange withdrawal interfaces

✗Fee penalty repeats on every transaction until the derivation path is changed

BIP84 (Native SegWit)

▸Addresses start with "bc1q" — Native SegWit pay-to-witness-public-key-hash format

▸30–40% smaller transaction data size than equivalent legacy transactions

▸Lower fees at any given sat/vbyte rate — the fee advantage is structural, not situational

▸Default in most modern wallets and exchanges; one setting change from legacy wallets

▸One-time confirmation; lower-fee path applies to every subsequent transaction automatically

Both columns describe fully valid Bitcoin addresses that confirm on the same network and reach any recipient. The only structural difference is data size — and data size directly determines fee cost at every fee rate. That is the answer to which derivation path is right for on-chain transactions: BIP84, for the same reason the same amount of work done more efficiently is preferable when the outputs are otherwise identical.

Confirming the Path Before Sending

The wallet setting that controls derivation path is typically found under "account type," "address format," or "derivation path" in preferences. Most modern wallets default to BIP84 and need no action. Wallets defaulting to BIP44 need one change that applies to all future addresses from that point forward. The prefix on the receiving address is the fastest confirmation that the right path is active.

Bitok Arena Research

Bitok Arena identified the three-step confirmation that any wallet is generating Native SegWit addresses before any on-chain Bitcoin transaction.

Address prefix check — "bc1q" confirms Native SegWit active; "1" confirms legacy; three seconds, covers any wallet that displays the address before broadcast.

Settings confirmation — wallets requiring manual switching list the option under "account type," "address format," or "derivation path"; done once, applies to all future addresses from that wallet.

Fee estimate review — wallets displaying pre-send fee estimates show the difference between legacy and Native SegWit directly in the interface before commitment.

A wallet generating bc1q addresses by default needs no further action. A wallet generating "1" addresses needs a one-time setting change. Either way, the confirmation takes under a minute and keeps every future transaction on the lower-fee path by default — a one-time check with permanent compounding savings across every subsequent on-chain send.

The Repeating Cost of the Wrong Default

A derivation path setting left on the shipping default is not a one-time cost — it is the same fee premium repeated on every transaction until the setting is corrected. For anyone sending on-chain Bitcoin with any regularity, the accumulated fee difference over dozens or hundreds of transactions is material. The technical terminology around derivation paths is a barrier to finding the right setting quickly, but the practical check requires only reading the address prefix and knowing what it means.

Bitok Arena Says

Bitok Arena's analysis finds BIP84 Native SegWit to be the lower-fee path for any on-chain Bitcoin send — 30–40% smaller transactions than BIP44 legacy at any fee rate. A wrong default does not cost once; it costs on every transaction sent from it. The prefix on the receiving address is the check that takes three seconds and costs nothing.

Whatever wallet a Bitcoin holder is using, confirming it generates BIP84 Native SegWit addresses is the single configuration check that keeps every future on-chain transaction on the most fee-efficient path. Both derivation paths produce valid addresses. Only one produces addresses that cost less to send from. The distinction is data structure — permanent, repeating, and correctable in under a minute.

Bitok Arena Bottom Line

Bitok Arena's analysis finds BIP84 to be the correct derivation path for on-chain Bitcoin transactions: it generates Native SegWit (bc1q) addresses that produce 30–40% smaller transactions and lower fees at any network rate than BIP44 legacy ("1") addresses. Both formats are fully valid on-chain. The prefix on a receiving address is the observable indicator of which path is active — bc1q means the lower-fee path.