Bitcoin Taproot Wallet Support Tracker: Which Wallets Support P2TR?

Taproot Wallet Support Overview

Taproot activated on the Bitcoin network at block 709,632 on November 14, 2021, introducing P2TR (Pay-to-Taproot) as a new output type. More than four years later, wallet support for Taproot remains uneven: most major wallets can send to and receive at bc1p addresses, but advanced features like MuSig2 key aggregation and Tapscript spending are available in only a handful of implementations.

The following tracker catalogs Taproot support across hardware, desktop, and mobile wallets. Each wallet is evaluated on five dimensions: P2TR receive (generating bc1p addresses), P2TR send-to (recognizing bech32m destinations), Schnorr signing (BIP 340), MuSig2 multisig (BIP 327), and Tapscript/advanced features. For a broader look at address format differences, see the Bitcoin wallet address types comparison.

Taproot Support Matrix

This table summarizes the current state of Taproot support across major Bitcoin wallets. "P2TR Receive" means the wallet can generate native bech32m addresses. "P2TR Send-to" means the wallet can construct transactions paying to bc1p destinations. "Schnorr" indicates the wallet uses BIP 340 Schnorr signatures for key-path spends. "MuSig2" tracks support for BIP 327 aggregated multisignatures. "Tapscript" covers script-path spending and advanced constructions like Miniscript on Taproot.

Hardware Wallet Support

All major hardware wallets now support basic Taproot operations, though the depth of support varies significantly. The key differentiator is whether a device supports only key-path spending (the simple case) or also script-path spending and advanced signing protocols.

Ledger

Ledger devices (Nano S Plus, Nano X, Stax, Flex) added P2TR support in the Bitcoin app v2.0.0 (November 2021). Users select "Taproot" as the account type when adding a Bitcoin account in Ledger Live. Ledger is the first major hardware wallet to ship MuSig2 support, added in Bitcoin app v2.4.0 (April 2025). This enables Taproot-native N-of-N multisig where multiple Ledger devices produce a single aggregated Schnorr signature, making the transaction indistinguishable from a single-signer spend on chain. Ledger also added Taproot Miniscript support in Bitcoin app v2.2.0, enabling script-path spending for compatible coordinator wallets.

Trezor

Trezor Safe 3, Safe 5, Model T, and Model One all support Taproot through Trezor Suite. Users choose "Taproot (P2TR)" during account creation, and the wallet generates bc1p addresses using the BIP 86 derivation path (m/86'/0'/0'). Required firmware versions: Model T and Safe 3 need firmware 2.4.3+, while Model One needs firmware 1.10.4+. Trezor currently supports BIP 86 key-path spending only, with no MuSig2 or Tapscript features.

Coldcard

Coldcard Mk4 and Q gained Taproot signing support in firmware v5.5.0, graduating from the experimental "Edge" branch where Taproot features had been available for testing. Coldcard offers the deepest Tapscript support of any hardware wallet: BIP 341 (Taproot), BIP 342 (Tapscript), and Miniscript/MiniTapscript with up to 8 tree leaves. This makes Coldcard a strong choice for developers building complex spending conditions with output descriptors. Earlier stable firmware (v5.0.3+) could verify P2TR output addresses in PSBTs for send-to functionality, but signing required the Edge firmware until the v5.5.0 release.

BitBox02, Keystone, Jade, and Passport

BitBox02 added Taproot in firmware v9.10.0 (March 2022), accessible through the BitBoxApp. One caveat: the anti-klepto protocol (protection against nonce covert channel attacks) is not available for Schnorr signatures on BitBox02, as the underlying library does not yet support it. Keystone 3 Pro supports P2TR through Sparrow Wallet (firmware 1.3.0+), though Taproot is not available through all companion apps. Blockstream's Jade added BIP 86 single-key Taproot signing in firmware v1.0.34 (March 2025), including xpub exports for Taproot derivation paths. Foundation's Passport gained full Taproot support in firmware v2.3.0 (February 2024), and its companion app Envoy unifies Taproot and SegWit accounts so users can manage both address types within a single account view.

Desktop Wallet Support

Desktop wallets generally offer the most complete Taproot support because they cater to power users and developers who need fine-grained control over transaction construction.

Bitcoin Core

Bitcoin Core provides the reference implementation of Taproot (BIPs 340, 341, 342). Version 22.0 (September 2021) activated Taproot consensus rules and added basic signing for P2TR descriptor wallets. Version 26.0 added Miniscript inside Taproot leaves. Bitcoin Core also added parsing of MuSig2 descriptors (BIP 390) for validation, though full MuSig2 signing remains an external workflow coordinated through PSBTs. New wallets default to P2WPKH (native SegWit), so users must explicitly create a tr() descriptor wallet to get P2TR addresses.

Sparrow Wallet

Sparrow is the preferred desktop wallet for Taproot among advanced users. It supports single-sig and multisig Taproot wallets with full coin control, descriptor-based account management, and hardware wallet integration. Sparrow added initial P2TR support in v1.4.3 (July 2021, testnet) and Taproot on Bitcoin Core via the Cormorant library in v1.7.2 (requires Core v24+). It also supports BIP 322 Taproot message signing (v1.7.8) and PayJoin with Taproot outputs.

Electrum and Wasabi

Electrum supports P2TR through the "Native SegWit (P2TR)" account type, using BIP 86 derivation. Wasabi Wallet added Taproot receive addresses in v2.2.0 (September 2024), allowing users to choose between SegWit and Taproot via a dropdown when generating a receiving address. Wasabi notes that spending a Taproot input is roughly 16% cheaper than spending a native SegWit input, making P2TR the more fee-efficient choice for CoinJoin participants. Both wallets default to native SegWit (bc1q) for new accounts.

Mobile Wallet Support

Mobile wallets have been slower to adopt Taproot receive addresses, though most can send to bc1p destinations. The gap is narrowing as wallets ship dedicated Taproot account types.

BlueWallet

BlueWallet added send-to-Taproot support in v6.2.14 (December 2021) and full BIP 86 Taproot HD wallets in v7.2.2 (November 2023), including send/receive, watch-only, hardware wallet integration, and coin control for Taproot accounts. Users create a Taproot wallet by selecting the P2TR option in the "Add Wallet" flow.

Muun and Green

Muun automatically generates Taproot addresses for new users and uses a novel approach where its 2-of-2 multisig architecture produces a single aggregated signature via MuSig, making the on-chain output indistinguishable from a standard single-key Taproot spend. Note that Muun uses submarine swaps for Lightning payments, meaning every Lightning transaction triggers an on-chain transaction.

Blockstream Green supports sending to bc1p addresses (since v3.7.6, November 2021) but does not yet offer Taproot receive addresses. Users cannot create a BIP 86 Taproot account in Green: the wallet still generates native SegWit addresses for deposits. Blockstream has indicated plans to add full Taproot receive support, but as of mid-2026 this feature remains unimplemented.

Phoenix and Lightning Taproot Channels

Phoenix Wallet introduced Taproot for on-chain swap-in deposits in v2.2.0 (February 2024) via the "Swaproot" protocol, which uses Taproot addresses with MuSig2 between the user and ACINQ's server. Version 2.7.1 (October 2025) added Taproot channels, making channel opens and splices roughly 15% cheaper and indistinguishable from regular single-signer P2TR transactions on chain. Existing channels are automatically upgraded to Taproot during the next on-chain operation.

Nunchuk, Envoy, and Zeus

Nunchuk stands out by offering both Taproot MuSig2 multisig (beta, December 2024) and native Miniscript support for Tapscript. Its MuSig2 implementation supports up to 5 keys (software keys only; hardware wallet signing is planned). Envoy (Foundation Devices) added full Taproot support in v1.5.1 (January 2024) and unified Taproot and SegWit into a single account view in v2.0.1 (July 2025). Zeus supports Taproot on-chain addresses (v0.8.0+) via BIP 86 derivation and was among the first mobile wallets to support Simple Taproot Channels through its embedded LND node.

Exchange and Service Support

Wallet support is only part of the adoption picture. If exchanges cannot send to bc1p addresses, users with Taproot wallets face friction when withdrawing funds.

Most major exchanges now support withdrawals to bc1p addresses, but many still use P2WPKH (native SegWit) for deposit address generation. For maximum compatibility when receiving from services, SegWit (bc1q) remains the safest default. See the address types deep dive for a full compatibility breakdown.

Why Taproot Matters

Taproot is more than an incremental address format upgrade. It introduces three BIPs that fundamentally expand what Bitcoin transactions can do:

• BIP 340 (Schnorr signatures): replaces ECDSA with Schnorr for key-path Taproot spends, enabling linear signature aggregation, batch verification, and simpler multisig constructions
• BIP 341 (Taproot): defines the P2TR output type, which commits to a public key and an optional MAST tree of spending scripts while revealing only the executed branch
• BIP 342 (Tapscript): updates the Bitcoin Script rules for Taproot, replacing OP_CHECKMULTISIG with OP_CHECKSIGADD and enabling future soft-fork extensibility via OP_SUCCESS opcodes

Together, these upgrades enable privacy (complex scripts look identical to simple spends on chain), efficiency (Schnorr key-path spends use fewer weight units than equivalent SegWit transactions), and future features like FROST threshold signatures, PTLCs for Lightning, and advanced covenant proposals. For a technical deep dive, see Taproot and Schnorr Signatures Explained.

Advanced Feature Support

The most important Taproot features for the ecosystem's future are not basic send/receive but the advanced signing protocols and scripting capabilities that Taproot enables.

MuSig2 (BIP 327)

MuSig2 allows N-of-N participants to produce a single Schnorr signature that is indistinguishable from a regular key-path spend. This means a 3-of-3 multisig transaction looks exactly like a single-signer transaction on chain, dramatically improving privacy and reducing fees. BitGo deployed MuSig2 Taproot multisig in production in 2023, achieving roughly 45% fee savings per input compared to native SegWit multisig. Ledger shipped hardware MuSig2 signing in Bitcoin app v2.4.0 (April 2025), and Nunchuk launched a Taproot MuSig2 multisig wallet in beta (December 2024). On the infrastructure side, the canonical C library libsecp256k1 v0.6.0 (November 2024) added a production MuSig2 module, and LND v0.21 (June 2026) graduated Simple Taproot Channels with MuSig2 to production status. For more detail, see the MuSig2 multisignatures explainer.

FROST Threshold Signatures

FROST extends the concept beyond MuSig2 by allowing M-of-N threshold signing: any subset of signers can authorize a transaction without revealing the threshold structure on chain. FROST was standardized by the IETF as RFC 9591 (June 2024) and assigned BIP 445 (January 2026, draft status). Frostsnap is shipping the first FROST-based hardware wallet, implementing a 2-of-3 architecture with distributed key generation. FROST is also used in production by the Spark protocol, where a user holds one key share while a set of independent operators collectively hold the other share via FROST. The ZF FROST library (Zcash Foundation) is the most mature implementation, reaching v3.0.0 (April 2026) with a dedicated frost-secp256k1-tr crate for Taproot. For more on threshold signing, see the FROST threshold signatures explainer.

Tapscript and Miniscript

Tapscript enables complex spending conditions to be embedded in a MAST tree, where only the executed branch is revealed on chain. Coldcard is the only hardware wallet with full Tapscript support (up to 8 leaves), while Ledger supports Taproot Miniscript (Bitcoin app v2.2.0+). Nunchuk offers native Miniscript support for constructing custom spending policies including timelocked inheritance plans and layered treasury approvals. Bitcoin Core v26.0 added Miniscript inside Taproot leaves at the RPC level. The combination of Tapscript and Miniscript enables structured spending policies (timelocks, multisig thresholds, backup keys) that are both human-auditable and machine-verifiable. Liana (Wizardsardine) is a dedicated vault wallet built on Miniscript descriptors with Taproot support, used for institutional custody and inheritance planning.

Taproot Adoption Statistics

Taproot adoption has followed an uneven trajectory since activation. Usage hit a single-day peak of roughly 76% of Bitcoin transactions on May 7, 2023, driven by the Ordinals inscription frenzy. Sustained adoption averaged around 42% through 2024 during peak Ordinals and Runes activity. As inscription volume declined, Taproot usage settled to approximately 20% of transactions by late 2025.

The UTXO picture tells a different story: P2TR accounts for roughly 34% of all UTXOs by count (the largest share of any script type), but holds only about 0.75% of total BTC value. This disparity exists because the vast majority of P2TR UTXOs are sub-1,000 sat inscription-related dust.

For context, native SegWit (v0) adoption has reached 90-95% of all transactions after roughly seven years. Taproot's organic (non-Ordinals) adoption follows a slower curve, partly because the fee savings over SegWit are smaller (roughly 15-16%) and partly because exchange and service support for bc1p deposit addresses remains incomplete. You can track adoption in real time at whentaproot.org.

What Blocks Broader Taproot Adoption

Several factors slow Taproot's path to ubiquity:

• Exchange deposit support: major exchanges like Coinbase and Binance still generate SegWit deposit addresses, creating friction for users who want to consolidate to a single Taproot wallet
• Wallet defaults: most wallets still default to native SegWit (P2WPKH) for new accounts, requiring users to explicitly select Taproot during setup
• Quantum computing discussions: the use of x-only public keys in Taproot outputs has prompted debate about long-term quantum resistance, with proposals like BIP-360 exploring post-quantum address formats (implemented on testnet by BTQ Technologies in March 2026)
• Tooling maturity: MuSig2 and FROST tooling is still early, limiting the practical benefits of Taproot's multisig privacy improvements for most users
• Incomplete wallet coverage: some popular wallets like Blockstream Green still lack Taproot receive addresses, which fragments the user experience

How to Choose a Taproot Wallet

The right wallet depends on which Taproot features you need:

• For basic Taproot send/receive with hardware security: Ledger, Trezor, BitBox02, or Passport paired with Sparrow or their native companion apps
• For MuSig2 multisig privacy: Ledger (v2.4.0+ Bitcoin app) with Nunchuk as the coordinator
• For advanced Tapscript and descriptor wallets: Coldcard (Mk4/Q with fw 5.5.0+) paired with Sparrow or Bitcoin Core
• For mobile-first Taproot: BlueWallet for on-chain, or Phoenix for Lightning with Taproot channels
• For privacy-focused Taproot: Wasabi (CoinJoin with Taproot outputs) or Sparrow with PayJoin
• For Miniscript-based vaults and inheritance: Nunchuk or Liana paired with Ledger or Coldcard

For a broader wallet selection guide, see the Bitcoin wallet selection tool.

Frequently Asked Questions

Which Bitcoin wallets support Taproot addresses?

Most major Bitcoin wallets now support P2TR addresses for sending and receiving. On hardware, Ledger, Trezor (all current models including Model One), Coldcard, BitBox02, Keystone, Jade, and Passport all support Taproot. On desktop, Bitcoin Core, Sparrow, Electrum, and Wasabi offer full P2TR support. On mobile, BlueWallet, Muun, Envoy, Nunchuk, Phoenix, and Zeus support Taproot. The notable exception is Blockstream Green, which can send to Taproot addresses but cannot yet generate them for receiving. The key differentiator is advanced features: only Ledger and Nunchuk currently support MuSig2, and only Coldcard supports full Tapscript with up to 8 leaves.

Is it safe to use a Taproot address as my primary Bitcoin address?

Yes. P2TR addresses are fully supported by the Bitcoin protocol since November 2021. The main practical concern is compatibility: a small number of older services cannot send to bc1p addresses. If you regularly receive from exchanges or services, verify that they support Taproot withdrawals before switching. For peer-to-peer transactions and modern wallet-to-wallet transfers, Taproot is the most efficient and private option available.

What is the difference between P2TR and P2WPKH?

P2WPKH (native SegWit v0) produces bc1q addresses and uses ECDSA signatures. P2TR (SegWit v1) produces bc1p addresses and uses Schnorr signatures. P2TR key-path spends are roughly 15-16% cheaper in virtual bytes than P2WPKH spends. P2TR also supports script-path spending via a MAST tree, enabling complex conditions (multisig, timelocks, hash locks) without revealing unused branches. For a full comparison of all address types, see the address types comparison tool.

Do I need to migrate my existing Bitcoin to a Taproot address?

No migration is required. Bitcoin at older address types (P2PKH, P2SH, P2WPKH) remains fully valid and spendable. If you want the fee and privacy benefits of Taproot, you can send your funds to a new P2TR address in your wallet. Be mindful of transaction fees when consolidating: batch the move during low-fee periods to minimize cost. The common input heuristic means combining UTXOs from different address types in a single transaction can reduce privacy.

What is MuSig2 and why does it matter for Taproot wallets?

MuSig2 is a two-round interactive signing protocol that lets multiple parties produce a single aggregated Schnorr signature. The result is a transaction that looks identical to a single-signer spend on chain, even though multiple keys were involved. This matters because traditional multisig transactions reveal the number of signers and the threshold in the on-chain script. MuSig2 hides this entirely, improving privacy and reducing transaction weight. BitGo's production deployment showed roughly 45% fee savings per input compared to native SegWit multisig. For more detail, see the MuSig2 multisignatures explainer.

How does Taproot improve Lightning Network channels?

Simple Taproot channels use P2TR outputs for channel funding transactions instead of P2WSH. This makes channel opens and cooperative closes indistinguishable from regular single-signer transactions, improving privacy. LND v0.21 (June 2026) graduated Simple Taproot Channels to production-ready status, using MuSig2 for cooperative closes. Phoenix Wallet's implementation also uses Taproot for splice transactions, reducing on-chain costs by roughly 15%. Taproot channels are a stepping stone toward PTLCs, which will replace HTLCs and further improve Lightning privacy by eliminating payment hash correlation across hops.

Will Taproot addresses be affected by quantum computing?

All current Bitcoin address types are theoretically vulnerable to quantum computers capable of breaking elliptic curve cryptography. Taproot's use of x-only public keys means the public key is directly visible in the output (unlike hashed formats like P2PKH), which has prompted some concern. However, this is a difference in exposure window, not fundamental security: once any address type is spent, the public key is revealed. The Bitcoin development community is actively exploring post-quantum options: BIP-360 was merged into the BIP repository in February 2026, and BTQ Technologies deployed it on testnet in March 2026. At current hardware capability levels, this remains a long-term research concern, not an immediate threat.

This tool is for informational purposes only and does not constitute financial advice. Wallet support data is based on publicly available documentation and release notes as of mid-2026. Features and firmware versions may change: always verify current support with the wallet vendor before making decisions.