Hi, not sure if I am following you. We already have taproot and multisig rows on software and hardware wallets comparisons. What do you exactly need?
I didn't test this myself, but according to post from one forum member, many wallets are not yet supporting multisig setup with taproot addresses.
He is not the only one claiming this, I also saw several discussions about this topic in social media before.
It seems that the mainstream Bitcoin multisig wallets like Electrum, Sparrow, and Specter do not yet support Taproot multisig.
I even asked this question to Brave AI and this is what was replied:
Design and Implementation of Multisig Taproot Wallets
Based on the provided search results, here’s a summary of the current state and future directions for multisig Taproot wallets:
Lack of Standardization: There is no standardized multisig Taproot wallet implementation yet. MuSig, a Schnorr key aggregation technique, is not yet standardized. BIPs 340 and 341 cover the introduction and use of Schnorr keys and Taproot spending rules, but they do not include standardized Taproot multisig wallets.
Hardware Wallet Implementations: Hardware wallet companies, such as Trezor, Ledger, and Coldcard, are working on implementing Taproot multisig wallets, but it’s a non-formal social standard. The Trezor team has been in contact with Casa and Unchained, and TBD on what other hardware wallet companies will do.
Software Wallet Implementations: Sparrow Wallet has not announced plans to support Taproot multisig wallets. Unchained has been discussing and planning for multisig Taproot wallets, but it’s a lengthy process, and they might take detours or hold off on implementation based on what they discover and what benefits their clients.
Research and Development: There are ongoing research and development efforts, such as the taproot-workshop GitHub repository, which provides a 3.1 degrading multisig case study. This project aims to explore Taproot descriptors and spending paths.
Future Directions: To achieve standardized multisig Taproot wallets, coordination between wallet developers and advisors is necessary. Unchained is leading the way in defining BCPs for multisig on Taproot, and hardware wallet vendors are working together to implement Taproot multisig wallets.
Key Takeaways:
No standardized multisig Taproot wallet implementation exists yet.
Hardware wallet companies are working on implementing Taproot multisig wallets, but it’s a non-formal social standard.
Software wallet implementations, such as Sparrow Wallet, have not announced plans to support Taproot multisig wallets.
Research and development efforts are ongoing, and Unchained is leading the way in defining BCPs for multisig on Taproot.
Coordination between wallet developers and advisors is necessary to achieve standardized multisig Taproot wallets.
Recommendations:
Follow updates from hardware wallet companies, such as Trezor, Ledger, and Coldcard, on their Taproot multisig wallet implementations.
Monitor Unchained’s progress on defining BCPs for multisig on Taproot and potential software wallet implementations.
Keep an eye on research and development efforts, such as the taproot-workshop GitHub repository, for insights into Taproot descriptors and spending paths.
Encourage coordination between wallet developers and advisors to achieve standardized multisig Taproot wallets.