<p>I have a non-HD wallet in Bitcoin Core v17.1.  I have never used SegWit before.  </p>

<p>I need to send some coins to a bech32 address from bitcoin-qt GUI.  The problem is after selecting the specific coin inputs to use (originally received into P2PKH address), and then entering the bc1... bech32 send to address, then the Send button does nothing.  I usually after pressing Send button get a passphrase prompt to unlock the wallet and confirm sending the transaction.</p>

<p>How do I send to a bech32 address from qt GUI?</p>

CC BY-SA 4.0
2019-05-28T03:04:06.260Z
This sounds like a bug that's unrelated to bech32 addresses.
Pieter Wuille
CC BY-SA 4.0
2019-05-29T02:21:54.667Z
Maybe it's a bug related to the selected inputs.  I'll upgrade to 18.0 soon and try again.  I'm also running on some older Linux qt libraries.
cranium
CC BY-SA 4.0
2019-09-29T21:54:42.937Z
When I upgraded bitcoin-qt, the problem was fixed.  Bug in 17.1
cranium
<bitcoin-core><segregated-witness><bech32-address>
Send to bech32 segwit address from Bitcoin Core 17.1
cranium
# Send to bech32 segwit address from Bitcoin Core 17.1

(Asked by: username_0 on 2019-05-28)

I have a non-HD wallet in Bitcoin Core v17.1. I have never used SegWit before.

I need to send some coins to a bech32 address from bitcoin-qt GUI. The problem is after selecting the specific coin inputs to use (originally received into P2PKH address), and then entering the bc1... bech32 send to address, then the Send button does nothing. I usually after pressing Send button get a passphrase prompt to unlock the wallet and confirm sending the transaction.

How do I send to a bech32 address from qt GUI?

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

> **Comments:**
> **username_1**: This sounds like a bug that's unrelated to bech32 addresses.  
> **username_0**: Maybe it's a bug related to the selected inputs.  I'll upgrade to 18.0 soon and try again.  I'm also running on some older Linux qt libraries.  
> **username_0**: When I upgraded bitcoin-qt, the problem was fixed.  Bug in 17.1  

---

## 0 answers

