<p>Bech32 is address encoding and cannot be enforced on the Bitcoin network as it is not part of the protocol. </p>

CC BY-SA 4.0
2018-11-29T22:45:06.897Z
2018-11-29T22:45:06.897Z
James C.
<p>Is it possible to make segwit transactions (and possibly segwit address: Bech32) mandatory in the Bitcoin Core code?</p>

<p>In other words, when a transaction is created using the wallet, the transaction should be bech32 based segwit
and when a transaction is passed to the node, the node should ensure its a segwit transaction with bech32 addresses.</p>

<p>This is a hard fork of Bitcoin and I am considering changing the code</p>

CC BY-SA 4.0
2018-11-26T03:40:13.197Z
Do you mean in the wallet code (so applying to transactions created and accepted), or in the consensus rules (applying to all transactions in the network)?
Pieter Wuille
CC BY-SA 4.0
2018-11-26T04:08:13.550Z
Both, in other words, nothing but segwit addresses using bech32 should be created, accepted or parsed.
picolo
CC BY-SA 4.0
2018-11-26T05:18:25.180Z
That requires a change to Bitcoin's network rules, which a vast agreement among the ecosystem. As such a change would break almost all wallet software, that seems highly unlikely to happen.
Pieter Wuille
CC BY-SA 4.0
2018-11-26T15:31:53.927Z
I am hard forking Bitcoin core by changing the code
picolo
<bitcoin-core><segregated-witness><bech32-address>
How to make segwit transaction and bech32 mandatory
picolo
# How to make segwit transaction and bech32 mandatory

(Asked by: username_0 on 2018-11-26)

Is it possible to make segwit transactions (and possibly segwit address: Bech32) mandatory in the Bitcoin Core code?

In other words, when a transaction is created using the wallet, the transaction should be bech32 based segwit
and when a transaction is passed to the node, the node should ensure its a segwit transaction with bech32 addresses.

This is a hard fork of Bitcoin and I am considering changing the code

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

> **Comments:**
> **username_1**: Do you mean in the wallet code (so applying to transactions created and accepted), or in the consensus rules (applying to all transactions in the network)?  
> **username_0**: Both, in other words, nothing but segwit addresses using bech32 should be created, accepted or parsed.  
> **username_1**: That requires a change to Bitcoin's network rules, which a vast agreement among the ecosystem. As such a change would break almost all wallet software, that seems highly unlikely to happen.  
> **username_0**: I am hard forking Bitcoin core by changing the code  

---

## 1 answers

### Answer by username_2 on 2018-11-29. Score: 1

Bech32 is address encoding and cannot be enforced on the Bitcoin network as it is not part of the protocol.


---

