<p>Many clients have not been updated to recognize native segwit addresses, and are unable to deal with the bech32.</p>

<p>There should be no real downside to sending to a non-native-segwit address, besides some minor fee increase when you spend the coins.</p>

CC BY-SA 4.0
2020-03-19T09:54:38.267Z
2020-03-19T09:54:38.267Z
Raghav Sood
<p>Bisq now does support extracting, withdrawing btc to Segwit addresses. They implemented this change back in Sept 2020 -&gt; see <a href="https://github.com/bisq-network/bisq/releases/tag/v1.4.2" rel="nofollow noreferrer">https://github.com/bisq-network/bisq/releases/tag/v1.4.2</a></p>
<p>Part of their Release notes in that version include:</p>
<blockquote>
<p>Use SegWit addresses to fund and withdraw from your Bisq wallet</p>
<p>NOTE: Although it's now finally possible to transfer out of Bisq to
Bech32 wallets, do not expect any fee savings just yet, because all
Bisq trading transactions still happen against P2PKH addresses. This
change will be shipped in one of the next releases.</p>
</blockquote>

CC BY-SA 4.0
2022-02-04T10:35:59.137Z
2022-02-04T10:35:59.137Z
Lioh Prez
<p>Every time I'm transferring over the funds from Bisq to Bitcoin Core, I get the error:</p>

<blockquote>
  <p>Invalid address.</p>
</blockquote>

<p>(Or something along those lines.)</p>

<p>Only after generating another receive address in Bitcoin Core, unchecking the "<strong><em>Generate native segwit (Bech32) address</em></strong>" checkbox, does it work.</p>

<p>Why does Bisq consider "native segwit (Bech32) addresses" (the default in Bitcoin Core) to be "invalid"? Is this some kind of internal war in the Bitcoin community where they refuse to even acknowledge the existence of this other "format"?</p>

<p>Every time it happens, I almost get a heart attack until I realize I forgot to uncheck that checkbox...</p>

<bitcoin-core><segregated-witness><bech32-address><bisq>
Why does Bisq claim that my "native segwit" receive addresses are "invalid"?
Parid
# Why does Bisq claim that my "native segwit" receive addresses are "invalid"?

(Asked by: username_0 on 2020-03-19)

Every time I'm transferring over the funds from Bisq to Bitcoin Core, I get the error:

> Invalid address.

(Or something along those lines.)

Only after generating another receive address in Bitcoin Core, unchecking the "***Generate native segwit (Bech32) address***" checkbox, does it work.

Why does Bisq consider "native segwit (Bech32) addresses" (the default in Bitcoin Core) to be "invalid"? Is this some kind of internal war in the Bitcoin community where they refuse to even acknowledge the existence of this other "format"?

Every time it happens, I almost get a heart attack until I realize I forgot to uncheck that checkbox...

**Tags:** bitcoin-core, segregated-witness, bech32-address, bisq


---

## 2 answers

### Answer by username_1 on 2020-03-19. Score: 2

Many clients have not been updated to recognize native segwit addresses, and are unable to deal with the bech32.

There should be no real downside to sending to a non-native-segwit address, besides some minor fee increase when you spend the coins.


---

### Answer by username_2 on 2022-02-04. Score: 0

Bisq now does support extracting, withdrawing btc to Segwit addresses. They implemented this change back in Sept 2020 -> see <https://github.com/bisq-network/bisq/releases/tag/v1.4.2>

Part of their Release notes in that version include:

> Use SegWit addresses to fund and withdraw from your Bisq wallet
>
> NOTE: Although it's now finally possible to transfer out of Bisq to
> Bech32 wallets, do not expect any fee savings just yet, because all
> Bisq trading transactions still happen against P2PKH addresses. This
> change will be shipped in one of the next releases.


---

