<p>As an answer didn't appear to be forthcoming, I did my own research in order to address this question.</p>
<p>Based on the information provided by the <a href="https://en.bitcoin.it/wiki/Bech32_adoption" rel="nofollow noreferrer">Bitcoin Wiki</a> on Bech32 adoption, I surmised the following information.</p>
<ol>
<li>All mainstream software wallets support <em>sending</em> to Bech32.</li>
<li>All mainstream hardware wallets support <em>sending</em> to Bech32 (either directly or via Electrum).</li>
<li>All major web wallets support <em>sending</em> to Bech32.</li>
<li>Most exchanges support <em>sending</em> to Bech32 (although notably Bitrex and LBC don't).</li>
</ol>
<p>Note that I have specified <em>sending</em> because a lot of these do not support receiving funds via a Bech32 address as of yet.  However, for my particular requirement that is unimportant as it is about sending only.</p>
<p>With the above facts confirmed, the answer I actually gave to my client was:</p>
<p><strong>Nearly all wallets can send to bech32 including most commercial wallet providers so you don't need to worry.</strong></p>
<p>When he asked what percentage, I was unable to answer it.  I would need to know what percentage of daily volume went through the exchanges that didn't support Bech32.  However, given then pretty much every wallet does support it I felt that this was less relevant.</p>

CC BY-SA 4.0
2020-09-17T06:41:51.413Z
It's difficult to give a definitive answer on the percentage, since it is difficult to know which wallets are creating transactions in the first place. Another good resource is the Optech compatibility matrix: https://bitcoinops.org/en/compatibility/, however that was created in 2019, and I don't know if all of it is up to date.
Murch
CC BY-SA 4.0
2020-09-01T20:59:47.653Z
2020-09-01T20:59:47.653Z
Martin
<p>For my client, I have set up a custom BTC payment solution using BTCPay Server.  The wallets I have configured in BTCPay Server produce only bech32 (<code>bc1xxx</code>) addresses for payments (cheapest transaction fees).</p>
<p>My client (who ordered the solution) has asked me how many of his customers would be <em>unable to send a payment to a bech32 address</em>?</p>
<p><strong>His concern is that his clients will be unable to pay their invoices in BTC because their wallets will be unable to send payments to the bech32 addresses.</strong></p>
<p>As I can see it, I can go back to my client with one of the following two answers:</p>
<ol>
<li>Nearly all (<code>??%</code>) of wallets can send to bech32 including all\most commercial wallet providers so you don't need to worry, or</li>
<li>This is a problem and instead of bech32 addresses I need to set up a payment wallet that supports legacy addresses (either <code>1xxx</code> or <code>3xxx</code>).</li>
</ol>
<p><strong>Could someone please tell me whether I can reassure him that the solution is fine as is, or whether I need to add legacy address support into it?</strong></p>

CC BY-SA 4.0
2020-08-21T19:44:44.677Z
@Prayank Thanks for your comment. I'm not looking for a wallet provider or utilising one that has a problem sending to bech32.  My question is asking what proportion of the market is unavailable to me as a payment recipient if I only accept payment to bech32 addresses.
Martin
<address><payment><bech32-address>
How Many Clients Could Not Send to Bech32 Addresses?
Martin
# How Many Clients Could Not Send to Bech32 Addresses?

(Asked by: username_0 on 2020-08-21)

For my client, I have set up a custom BTC payment solution using BTCPay Server. The wallets I have configured in BTCPay Server produce only bech32 (`bc1xxx`) addresses for payments (cheapest transaction fees).

My client (who ordered the solution) has asked me how many of his customers would be *unable to send a payment to a bech32 address*?

**His concern is that his clients will be unable to pay their invoices in BTC because their wallets will be unable to send payments to the bech32 addresses.**

As I can see it, I can go back to my client with one of the following two answers:

1. Nearly all (`??%`) of wallets can send to bech32 including all\most commercial wallet providers so you don't need to worry, or
2. This is a problem and instead of bech32 addresses I need to set up a payment wallet that supports legacy addresses (either `1xxx` or `3xxx`).

**Could someone please tell me whether I can reassure him that the solution is fine as is, or whether I need to add legacy address support into it?**

**Tags:** address, payment, bech32-address

> **Comments:**
> **username_0**: @Prayank Thanks for your comment. I'm not looking for a wallet provider or utilising one that has a problem sending to bech32.  My question is asking what proportion of the market is unavailable to me as a payment recipient if I only accept payment to bech32 addresses.  

---

## 1 answers

### Answer by username_0 on 2020-09-01. Score: 1 | Accepted answer

As an answer didn't appear to be forthcoming, I did my own research in order to address this question.

Based on the information provided by the [Bitcoin Wiki](https://en.bitcoin.it/wiki/Bech32_adoption) on Bech32 adoption, I surmised the following information.

1. All mainstream software wallets support *sending* to Bech32.
2. All mainstream hardware wallets support *sending* to Bech32 (either directly or via Electrum).
3. All major web wallets support *sending* to Bech32.
4. Most exchanges support *sending* to Bech32 (although notably Bitrex and LBC don't).

Note that I have specified *sending* because a lot of these do not support receiving funds via a Bech32 address as of yet. However, for my particular requirement that is unimportant as it is about sending only.

With the above facts confirmed, the answer I actually gave to my client was:

**Nearly all wallets can send to bech32 including most commercial wallet providers so you don't need to worry.**

When he asked what percentage, I was unable to answer it. I would need to know what percentage of daily volume went through the exchanges that didn't support Bech32. However, given then pretty much every wallet does support it I felt that this was less relevant.

> **Comments:**
> **username_1**: It's difficult to give a definitive answer on the percentage, since it is difficult to know which wallets are creating transactions in the first place. Another good resource is the Optech compatibility matrix: https://bitcoinops.org/en/compatibility/, however that was created in 2019, and I don't know if all of it is up to date.  

---

