[LIST] Wallets supporting Taproot

[dkbit98]

Taproot has been successfully activated on November 14 at block height 709632, and that is a great step forward for better privacy on bitcoin blockchain.
It needs time for all wallets, services and exchanges to update and add support for Taproot but it should be much quicker than it was in case of segwit fork.

Some wallets already started supporting Taproot and I will follow updates and changes in this topic:

Software wallets supporting Taproot:

• Bitcoin Core
• Sparrow wallet
• Specter wallet
• Fully Noded
• Nunchuk*
• Muun wallet*
• Zeus wallet*
• MyCitadel
• Blixt wallet* ^LN
• Breez wallet* ^{LN dev console}
• Unstoppable wallet*
• Bitmask
• Phoenix* ^LN
• Exodus wallet
• Envoy*
• Mutiny*
• Electrum (partial)
• Green wallet (partial)
• Blue wallet* (partial)

* Mobile wallet

Hardware wallets supporting Taproot:

• Passport
• Trezor
• BitBox02
• OneKey
• SeedSigner DIY
• Keystone (v 1.3.0 with Sparrow)
• Jade (partial)
• Satochip (beta)
• ColdCard (experimental)
• SecuX closed source
• Ledger closed source
• Safepal closed source

Ledger wallet is the first hardware wallet with Taproot support and they made this available as experimental feature with their latest update of Ledger Live v2.35 desktop, using Bitcoin app 2.0.0.
Trezor and Jade wallet will probably Taproot release updates in December.

[1713889804]

1713889804

[1713889804]

1713889804

[1713889804]

1713889804

[Charles-Tim]

About BlueWallet which I have just updated (on playstore), I have not seen it supporting P2TR yet, maybe I am not getting it right. Only what are supported yet are:

• Segwit (P2WPHK) which is generated by default
• Lightning Network
• Vault, which is a 2-of-3 multisig (P2WSH) wallet

Or, maybe, segwit is generated by default while possible to import P2TR seed phrase and work perfectly, but I have not tried this and I am not certain if it can work that way using P2TR derivational path.

[dkbit98]

About BlueWallet which I have just updated (on playstore), I have not seen it supporting P2TR yet, maybe I am not getting it right. Only what are supported yet are:

You are right,  Taproot is not supported yet in Blue wallet and I corrected my mistake.
Thanks.

[RickDeckard]

Nice thread OP. In order to help you to keep track of how services / wallets are being updated to Taproot (Bech32m) I think you'll find this[1] list very useful (as a complement to your thread).
All the information matches with the one that you provided. Glancing at the list I see that maybe you could add Fully Noded[2] as another software wallet that has updated to Taproot?
[1]https://en.bitcoin.it/wiki/Bech32_adoption
[2]https://twitter.com/FullyNoded/status/1438652812410298370

[dkbit98]

Glancing at the list I see that maybe you could add Fully Noded[2] as another software wallet that has updated to Taproot?

Thanks for suggestion.
I added Fully Noded wallet to the list, but I honestly never heard about it until now, maybe because it's only supporting MacOS and iOS.

[Pmalek]

According to this announcement by Blockstream, their Blockstream Green wallet will soon support Taproot (if it hasn't already been activated in the meantime). If you want, you can keep an eye on their blog. That post I linked to is currently their newest blog entry. 

Cash App has also announced that they will support Taproot. All their customers should have it activated until December 2021.

[SFR10]

While I was scrolling through the link @RickDeckard provided, I noticed they've labeled "Bitcoin Knots as Starting with 22.0" but if I'm reading and understanding everything correctly, they've already released that version "9 days ago ^{[having said those, I'm not sure if it's worth adding it since it's a fork of Bitcoin Core with some added features]}". Apart from that, it seems that BitGo also supports it: Taproot Support for BitGo Wallets ^{[credit goes to @RickDeckard]}
To those who know about coding stuff:

• Is there a "big difference ^{[in terms of the effort that's needed for coding it]}" between partially supporting it ^{[e.g. Wallet of Satoshi]} and full support like the ones on the list?

[pooya87]

Here is an issue tracking the Taproot support in Electrum: https://github.com/spesmilo/electrum/issues/7544

There is no ETA yet and it seems like the support takes a lot of effort and may take some time since they plan to do some refactoring and haven't decided on details (seed version, derivation path, extended key scheme, etc).

[dkbit98]

Trezor hardware wallet just released new December update and they are adding Taproot support, being second hardware wallet to do this after ledger.
If you have Trezor Model One you will need to update latest firmware version 1.10.4, and for Trezor Model T that is version 2.4.3.
They added more small fixes and improvements in this update, and note that it may take some time until update is shown in your Trezor Suite app.
After this update you will have new Account type option and Taproot addresses BIP86, P2TR, Bech32m.


https://blog.trezor.io/trezor-suite-and-firmware-updates-december-2021-d1e74c3ea283

[dkbit98]

List of wallets is updated today.
BitBox02 is third hardware wallet that is now officially supporting Taproot addresses after updating to latest firmware v9.10.0 and app version 4.32.0.
This was expected update for me after Trezor released their support, knowing that Bitbox is based on modified Trezor code, but it's nice to see more wallets that support Taproot.
You can see more details about this update ontheir blog page, and inspect open source code on their github page:


https://shiftcrypto.ch/blog/bitbox-03-2022-glaernisch-update/
https://github.com/digitalbitbox/bitbox02-firmware/releases

[SFR10]

Earlier this month, "Nunchuk" also added support for Taproot addresses:
^{- I only checked their Android app, but it's not limited to that OS + it's still in beta mode!}

• 

Not sure if the above lists are limited to SW and HW wallets only, but there are also a couple of web wallets ^{[Bitnob and BitGo]} with Taproot support.

[dkbit98]

Earlier this month, "Nunchuk" also added support for Taproot addresses:
^{- I only checked their Android app, but it's not limited to that OS + it's still in beta mode!}

I added Nunchuk wallet and updated the list, thanks to SFR10 for posting his suggestion.
I noticed this wallet some time ago and it has some interesting features, but I never managed to test it myself so far, but I downloaded it now.
Interesting feature that is offering is Air-gapped signing, and no single points of failure, but I am not sure how exactly that works.

[pooya87]

I think your list has to stick to popular and reviewed wallets that support Taproot instead of any random low quality ones that add the support. Or at least clarify that your list is not an endorsement of the said wallets. For example I took a quick look at Nunchuk and their repository doesn't look very active after 2 years and the wallet is definitely not popular. I don't think anybody has ever reviewed this.

[nc50lc]

• Bitcoin Core ^{(manual import)}

-snip-

You can update this now, no need for manual import through the console/command.
Bitcoin Core version 23.0 now creates descriptor wallets with Taproot parent descriptors by default.

And it's now possible to request Bitcoin taproot "bech32m" address from the GUI's receive tab if the wallet has the parent descriptor:


Reference:

Wallet

• Descriptor wallets are now the default wallet type. Newly created wallets
  will use descriptors unless descriptors=false is set during createwallet, or
  the Descriptor wallet checkbox is unchecked in the GUI.
  
  
• Newly created descriptor wallets will contain an automatically generated tr()
  descriptor which allows for creating single key Taproot receiving addresses.
  

[dkbit98]

You can update this now, no need for manual import through the console/command.
Bitcoin Core version 23.0 now creates descriptor wallets with Taproot parent descriptors by default.

Thank you for reporting.
List is now updated and manual import removed from Bitcoin Core wallet.

No new wallets to report, but Keystone hardware wallet is currently working on adding Taproot support and they should be fourth hardware wallet that supports it, after Ledger, Trezor and BitBox02.

[BitcoinGirl.Club]

If I understand correctly then Taproot is 4th type of address format.

Legacy start with a 1
Nested SegWit starts with a 3
Native SegWit stars with bc1

How to identify Taproot address?
What are the advantages it has over a bech32 address?

This verity are going to be overwhelming and for someone like me who is old school it is going to be hard to remember 🙄

[Charles-Tim]

If I understand correctly then Taproot is 4th type of address format.

Legacy start with a 1
Nested SegWit starts with a 3
Native SegWit stars with bc1

How to identify Taproot address?
What are the advantages it has over a bech32 address?

This verity are going to be overwhelming and for someone like me who is old school it is going to be hard to remember

You can read this to know about the transaction fee advantage segwit version 0 (native segwit) has over segwit version 1 (pay-to-taproot).

Pay-to-taproot (P2TR) transaction fee

BIP 86: m/86'/0'/0'/0/0 > Taproot
Key Derivation for Single Key P2TR Outputs
For low output and more input transaction, like consolidation, pay-to-taproot fee is lesser
For low input and more output transaction, the fee for native segwit (version 0) is lesser (a very good advantage)
For the same input and output, the fees are almost the same for version 0 (bc1q addresses) and version 1 (bc1p addresses)

For multisig. Transaction will be indistinguishable as a result of key aggregation, even 15-of-15 multisig will have the same fee like a transaction made from single pubkey wallet.

Also it can help in lightning network while closing a channel, both party can join their signatures together to make a single one which will also reduce transaction fee. It makes key aggregation possible and generate a single key and schnorr signature.

With the help of adaptor signature, atomic swap is possible.

The difference in both addresses
bc1q... For native segwit (segwit version o)
bc1p... For pay-to-taproot (segwit version 1)

q is the witness version 0 for native segwit, p is the witness version 1 for pay-to-taproot.

[witcher_sense]

What are the advantages it has over a bech32 address?

I am not a technically competent person, but I will try to explain. bech32 encoding scheme contains a sophisticated error detection mechanism that can identify up to four mistypes in an address, and in some cases, it can tell you where those errors occurred. However, this scheme has a serious vulnerability which is called  "length extension mutation weakness" which in layman's terms means "it is possible to slightly alter bech32 address in such a way that doesn't invalidate checksum." In other words, if you accidentally make a typo in the address, your wallet still accepts it as valid, but you may lose your coins because there is no corresponding private key to an altered address. bech32m fixes this vulnerability by introducing a new checksum algorithm.

You can read more here:

https://bitcoinops.org/en/topics/bech32/
https://bitcoin.stackexchange.com/questions/101117/what-problems-identified-with-bech32-addresses-have-been-resolved-with-the-updat
https://bitcoin.stackexchange.com/questions/91602/how-does-the-bech32-length-extension-mutation-weakness-work
https://river.com/learn/terms/b/bech32-modified/
https://github.com/sipa/bech32/issues/51

[suzanne5223]

In addition to the answer that was previously provided. You can distinguish native Segwit address and tap root by looking at the 4th letter i.e tap root has "P" while native Segwit has "Q".
With taproot transactions verification on the Bitcoin network is easier and more effective. It aids lower tx fees and also improves privacy.

[BitcoinGirl.Club]

<snip>

You left me a whole lot of reading and it's gonna take me time to understand the entire idea. Thanks.

"it is possible to slightly alter bech32 address in such a way that doesn't invalidate checksum." In other words, if you accidentally make a typo in the address, your wallet still accepts it as valid, but you may lose your coins because there is no corresponding private key to an altered address. bech32m fixes this vulnerability by introducing a new checksum algorithm.

I usually copy and paste an address then I check first few character and last few characters. It's too much to check all the characters for a human I think. But anyway, I assume Legacy and Nested segwit does not have this checksum issue.

In addition to the answer that was previously provided. You can distinguish native Segwit address and tap root by looking at the 4th letter i.e tap root has "P" while native Segwit has "Q".

I never thought of it, are bitcoin addresses case sensitive?

Dumb fu**, I should have known better 🤣
I am an embarrassment for a Legendary rank LOL