<p>Not all addresses beginning with a <code>3</code> are multisig, and Bitcoin Core does not make you multisig addresses. Addresses beginning with a <code>3</code> are P2SH addresses. The segwit addresses Bitcoin Core generates by default are segwit scripts nested in a P2SH address in order to allow for backwards compatibility. If you want to use the native segwit addresses (bech32 addresses that begin with <code>bc1</code>), you can start Bitcoin Core with <code>-addresstype=bech32</code> or go to the receive tab to get a new address and check the "Use bech32" checkbox.</p>

CC BY-SA 3.0
2018-03-02T23:08:54.610Z
That's the answer. Thanks! Yes, default is P2SH-segwit for now. I think there should be a warning or a prompt for it while upgrading. Some users may not know use of P2SH addresses will result in higher fees.
uykusuzessek
CC BY-SA 3.0
2018-03-02T23:16:47.250Z
Edit: this transaction has only P2SH inputs but its fee rate is low (36.357 sat/B) : https://blockchain.info/tx/2af3330feaeeb92d96531289ca242384f54b6070a1e3a2bf1a12e6343d920583 do you know why? Do we really need bech32 addresses for low fees?
uykusuzessek
CC BY-SA 3.0
2018-03-02T23:18:06.277Z
P2SH nested segwit inputs still have lower fees than legacy. They have higher fees than native segwit. The fee info shown on block explorers are not always correct, especially since fees should really be in fee/weight unit not fee/byte.
Ava Chow
CC BY-SA 3.0
2018-03-02T22:40:23.103Z
2018-03-02T22:40:23.103Z
Ava Chow
<p>I just downloaded the version 0.16 and tried to generate a new address via GUI while syncing <strong>mainnet</strong> blocks. I have never activated multi-signature but it gave me an address starting with "3". As far as I know, segwit addresses currently start with "bc1q". Can someone tell me what's going on?</p>

<bitcoin-core><segregated-witness><multi-signature>
Bitcoin Core 0.16 new address prefix
uykusuzessek
# Bitcoin Core 0.16 new address prefix

(Asked by: username_0 on 2018-03-02)

I just downloaded the version 0.16 and tried to generate a new address via GUI while syncing **mainnet** blocks. I have never activated multi-signature but it gave me an address starting with "3". As far as I know, segwit addresses currently start with "bc1q". Can someone tell me what's going on?

**Tags:** bitcoin-core, segregated-witness, multi-signature


---

## 1 answers

### Answer by username_1 on 2018-03-02. Score: 1 | Accepted answer

Not all addresses beginning with a `3` are multisig, and Bitcoin Core does not make you multisig addresses. Addresses beginning with a `3` are P2SH addresses. The segwit addresses Bitcoin Core generates by default are segwit scripts nested in a P2SH address in order to allow for backwards compatibility. If you want to use the native segwit addresses (bech32 addresses that begin with `bc1`), you can start Bitcoin Core with `-addresstype=bech32` or go to the receive tab to get a new address and check the "Use bech32" checkbox.

> **Comments:**
> **username_0**: That's the answer. Thanks! Yes, default is P2SH-segwit for now. I think there should be a warning or a prompt for it while upgrading. Some users may not know use of P2SH addresses will result in higher fees.  
> **username_0**: Edit: this transaction has only P2SH inputs but its fee rate is low (36.357 sat/B) : https://blockchain.info/tx/2af3330feaeeb92d96531289ca242384f54b6070a1e3a2bf1a12e6343d920583 do you know why? Do we really need bech32 addresses for low fees?  
> **username_1**: P2SH nested segwit inputs still have lower fees than legacy. They have higher fees than native segwit. The fee info shown on block explorers are not always correct, especially since fees should really be in fee/weight unit not fee/byte.  

---

