Posted by murch
Nov 10, 2026/20:31 UTC
Determining which services currently support bc1p addresses, specifically those utilizing bech32m encoding for P2TR (Taproot) outputs, involves referencing curated resources. The website whentaproot.org provides up-to-date information on wallets and services that have implemented support for these address types. Additionally, the Bech32 adoption page on the Bitcoin Wiki offers an extended list of entries, including some that may not yet appear on whentaproot.org. These two references together offer a reliable approach to monitoring adoption rates and compatibility.
Waiting for universal support for creation and acceptance of P2TR outputs and bech32m addresses risks stagnating broader adoption. Relying solely on complete ecosystem readiness could result in progress being hindered by slower-moving entities, creating a classic chicken-and-egg scenario. Proactive usage and increased demand for P2TR can serve as incentives for remaining services to expedite their own implementation processes, ultimately fostering widespread compatibility more efficiently.
These insights are informed by direct contributions to both whentaproot.org and the relevant Bitcoin Wiki documentation, reflecting a position of authority and engagement within the ongoing development and documentation of Taproot and associated standards.
Thread Summary (8 replies)
Nov 8 - Nov 13, 2026
9 messages
TLDR
We’ll email you summaries of the latest discussions from high signal bitcoin sources, like bitcoin-dev, lightning-dev, and Delving Bitcoin.
We'd love to hear your feedback on this project.
Give Feedback