Should wallets default to Taproot or SegWit receive addresses while some services still reject bc1p?

Posted by Anzus_GemWallet

Nov 8, 2026/13:33 UTC

Address compatibility continues to be a significant challenge for cryptocurrency wallet users, particularly when dealing with the various formats supported by different services. Users frequently encounter issues when withdrawing funds from exchanges or other platforms to their Gem Wallet receive address, only to be met with an "invalid address" error. This situation often arises when the user’s wallet generates a Taproot (bc1p…) address, which, despite being valid according to Bitcoin standards, is not universally recognized by all sending services.

Wallet teams face critical decisions regarding the default address format used for receiving transactions. The choice between Taproot (bc1p…) and SegWit (bc1q…) addresses involves balancing future-proofing against current compatibility. Some wallets may opt for Taproot by default to encourage adoption of the latest protocol improvements, while others might prioritize SegWit due to its broader acceptance across exchanges and services. Factors influencing this decision typically include the prevalence of support among major platforms and the desire to provide users with a seamless experience.

When both Taproot and SegWit options are available, presenting the choice to the user becomes a delicate matter. The selection interface must be accessible enough that users can locate and utilize it when encountering compatibility problems, yet discreet enough not to overwhelm those unfamiliar with the technical differences. Effective UI/UX design is essential to ensure that users can find alternative address formats as needed, without introducing confusion or complexity to the majority who may never need to switch.

Service-side support for newer address formats like bc1p remains inconsistent. There is currently no definitive, up-to-date resource listing which exchanges and services accept Taproot addresses, leaving many users and wallet teams reliant on trial and error. This lack of transparency underscores the need for better communication within the ecosystem and possibly the creation of community-maintained resources, such as a compatibility database, to help users and developers navigate these evolving standards.

Link to Raw Post
Bitcoin Logo

TLDR

Join Our Newsletter

We’ll email you summaries of the latest discussions from high signal bitcoin sources, like bitcoin-dev, lightning-dev, and Delving Bitcoin.

Explore all Products

ChatBTC imageBitcoin searchBitcoin TranscriptsSaving SatoshiDecoding BitcoinWarnet
Built with 🧡 by the Bitcoin Dev Project
View our public visitor count

We'd love to hear your feedback on this project.

Give Feedback