Bitcoin SegWit & Taproot Adoption Tracker

Current SegWit and Taproot Adoption Rates

Bitcoin's two most significant soft fork upgrades, SegWit (activated August 2017) and Taproot (activated November 2021), have reshaped how transactions are constructed on the network. SegWit introduced the witness discount that reduces fees and fixed transaction malleability, while Taproot brought Schnorr signatures and a more flexible scripting model via BIP-341.

As of early 2026, approximately 85-90% of Bitcoin transactions spend at least one SegWit input. Taproot adoption has been more volatile: it peaked above 40% in early 2024 driven by Ordinals and Runes activity, then settled back to roughly 15-20% as inscription demand cooled. The following table summarizes the current state.

For a detailed breakdown of how each address format works, see the Bitcoin address format guide and the research deep dive on address types from P2PKH to Taproot.

Historical Adoption Curves

SegWit adoption followed a predictable S-curve. After activation in August 2017, uptake was slow: fewer than 15% of transactions used SegWit by early 2018. A rapid jump to 30% occurred in March 2018 as major wallets shipped updates. By October 2018 adoption hit 40%, crossed 50% in mid-2019, and reached 62% by January 2020. The pace continued steadily, passing 70% in 2021 and reaching approximately 87% by 2022, where it has largely plateaued.

Taproot's trajectory has been different. After a quiet first year hovering near 1-2% adoption, the launch of Ordinals inscriptions in early 2023 pushed Taproot usage to around 4%. The BRC-20 token standard and later the Runes protocol drove Taproot transactions past 39% by January 2024. On the Runes launch day (April 23, 2024), Runes-related transactions accounted for over 81% of network activity. As speculative activity cooled through late 2024 and 2025, Taproot's share settled back to 15-20%, reflecting organic adoption from wallets and protocols rather than inscription-driven volume.

The contrast is instructive: SegWit adoption was driven by wallets and exchanges upgrading infrastructure for fee savings, producing steady growth. Taproot adoption has been driven more by novel use cases (inscriptions, tokens) that create sudden demand spikes. Organic Taproot adoption from wallets defaulting to P2TR addresses remains a slower process.

Transaction Size and Fee Impact

The practical motivation for adopting SegWit and Taproot is fee reduction. The witness discount introduced by SegWit counts signature data at 0.25 weight units per byte instead of 1.0, making transactions cheaper in terms of virtual bytes (vB). For a standard single-input, two-output transaction:

• P2PKH (legacy): ~226 vB
• P2SH-P2WPKH (wrapped SegWit): ~172 vB
• P2WPKH (native SegWit): ~141 vB
• P2TR (Taproot): ~142 vB for key-path spend, but witness data per input is ~16.5 vB vs ~27 vB for P2WPKH

At a fee rate of 20 sat/vB, the difference between a legacy P2PKH transaction and a native SegWit P2WPKH transaction is roughly 1,700 satoshis per input. For transactions with many inputs (such as UTXO consolidations), the savings compound significantly. See the transaction size reference for detailed byte-level breakdowns across all address types.

Taproot's key-path spend is comparable in size to P2WPKH for single-signature transactions, but Taproot shines in multisig and complex script scenarios. A MuSig2 aggregated Taproot key-path spend looks identical to a single-signature spend on-chain, dramatically reducing the cost of threshold signature transactions and improving privacy.

Wallet Support Matrix

Wallet defaults are the single largest driver of address type adoption. Most wallets now support SegWit natively, but Taproot defaults remain uncommon. The following matrix covers major wallet categories.

Bitcoin Core is notable as one of the few wallets that defaults to Taproot (P2TR) for new descriptor-based wallets since version 24.0. Most consumer wallets default to native SegWit (P2WPKH) and offer Taproot as an opt-in account type. This conservative approach makes sense: P2WPKH has universal compatibility, while some older services still cannot send to Bech32m-encoded Taproot addresses. For a broader wallet comparison, see the hardware wallet comparison.

Exchange Support

Exchange adoption directly impacts network-wide statistics because exchanges process a large share of Bitcoin transactions. Support levels vary between deposits (receiving) and withdrawals (sending).

Kraken stands out as the exchange with the most complete Taproot support, offering both deposit and withdrawal functionality. Most exchanges use native SegWit (bc1q) addresses for customer deposits and support sending to Taproot addresses, but do not generate Taproot deposit addresses for user accounts. This asymmetry means exchange deposits remain overwhelmingly SegWit, which contributes to the gap between SegWit and Taproot adoption metrics at the network level.

Why SegWit Adoption Plateaued

SegWit adoption has hovered around 85-90% since 2022. The remaining 10-15% of non-SegWit transactions come from several sources:

• Legacy wallets and services that have not upgraded
• Older UTXOs locked to P2PKH addresses being spent
• Custodial services running legacy infrastructure
• Deliberate use of P2SH for backward-compatible multisig setups
• Mining pool payout systems using legacy address types

Complete SegWit adoption is unlikely because legacy UTXOs will continue to exist on-chain indefinitely. Every time someone spends from an old P2PKH address, that transaction counts as non-SegWit regardless of the destination format.

What Is Driving Taproot Adoption

Taproot's adoption story has two distinct chapters. The first is organic wallet adoption, which has been gradual as wallet developers integrate BIP-86 derivation paths and Bech32m encoding. The second, and more dramatic, driver has been the Ordinals and token ecosystem.

Ordinals inscriptions store arbitrary data in Taproot witness fields, which means every inscription transaction is a Taproot transaction. The BRC-20 token standard and the Runes protocol (launched April 2024) similarly rely on Taproot. At their peak, these protocols pushed Taproot usage above 40% of all transactions. As speculative interest waned, the percentage dropped, but organic adoption from wallets and Schnorr-based protocols continues to build a higher floor.

Looking ahead, several protocol developments should accelerate Taproot adoption: FROST threshold signatures, MuSig2 multisignatures, and Miniscript policy descriptors all benefit from Taproot's key-path and script-path spending model. Layer 2 protocols like Spark also leverage Taproot for more efficient on-chain footprints.

Validating Address Types

To check which address format a specific Bitcoin address uses, the address validator tool decodes any address and identifies its type (P2PKH, P2SH, P2WPKH, P2WSH, or P2TR). This is useful when verifying wallet configurations or debugging compatibility issues between services.

For encoding-level details, the Bech32 encoder demonstrates the difference between Bech32 (used by SegWit v0 addresses) and Bech32m (used by Taproot v1 addresses), as specified in BIP-350.

Frequently Asked Questions

What percentage of Bitcoin transactions use SegWit?

Approximately 85-90% of Bitcoin transactions spend at least one SegWit input as of early 2026. This figure has been relatively stable since 2022, when adoption crossed the 85% mark. The remaining 10-15% comes from legacy P2PKH outputs being spent and services that have not upgraded to SegWit.

What is the current Taproot adoption rate?

Taproot transactions account for roughly 15-20% of Bitcoin network activity in early 2026. This is down from a peak above 40% in early 2024, which was driven by Ordinals inscriptions and the Runes protocol launch. The current rate reflects organic wallet adoption rather than speculative inscription activity.

How much do SegWit transactions save on fees?

A native SegWit (P2WPKH) transaction is approximately 141 virtual bytes for a standard 1-input, 2-output payment, compared to 226 vB for legacy P2PKH. That is a roughly 38% reduction in fees. Wrapped SegWit (P2SH-P2WPKH) saves about 24%. Taproot key-path spends offer similar or slightly better savings than native SegWit, with the greatest advantage in multisig and complex script scenarios.

Why don't all wallets default to Taproot?

Most wallets default to native SegWit (P2WPKH) because it has universal compatibility across exchanges and services. Some older platforms still cannot send to Bech32m-encoded Taproot addresses. Wallet developers are cautious about switching defaults until Taproot receiving support is ubiquitous. Bitcoin Core is one of the few wallets that defaults to Taproot for new descriptor-based wallets (since v24.0).

Did Ordinals increase Taproot adoption?

Yes, dramatically. Ordinals inscriptions are stored in Taproot witness data, so every inscription is a Taproot transaction. The launch of Ordinals in early 2023 pushed Taproot from under 2% to over 13%, and subsequent BRC-20 and Runes activity drove it above 40% by early 2024. When inscription volume declined, Taproot's share dropped accordingly, but the baseline organic adoption remained higher than pre-Ordinals levels.

How does Taproot improve Bitcoin privacy?

Taproot's key-path spend makes all single-signature, multisig, and complex script transactions look identical on-chain: they all appear as a single Schnorr signature spending from a bc1p address. This means an observer cannot distinguish a simple payment from a multisig spend or a hash time-locked contract. This uniformity improves transaction privacy significantly compared to SegWit, where P2WSH multisig scripts reveal the number of signers and threshold on-chain.

Will SegWit adoption ever reach 100%?

Almost certainly not. Legacy P2PKH UTXOs exist permanently on the blockchain. Every time an old P2PKH output is spent, that transaction counts as non-SegWit on the input side. Additionally, some niche use cases and older custodial systems continue to generate legacy transactions. The practical ceiling for SegWit adoption is likely in the low 90s as a percentage of total transactions.

This tool is for informational purposes only and does not constitute financial advice. Adoption percentages are approximate and based on publicly available on-chain data from sources including transactionfee.info and Glassnode. Figures fluctuate daily and should be verified against current chain analytics before making technical or business decisions.