<p>In general spending from a segwit output (i.e. "sending from" a segwit address) will be cheaper than spending a non-segwit output (i.e. "sending from" a non-segwit address). So yes, if you "send from" a bech32 address, it will be cheaper than "sending from" a P2PKH address.</p>

CC BY-SA 3.0
2017-11-06T16:22:14.693Z
My coins are on mycellium now and I'm assuming I can't send these coins to a bc1 address. How do you suggest I move it into electrum? Do I just do a sweep?
Patoshi パトシ
CC BY-SA 3.0
2017-11-06T16:23:01.613Z
Import your seed phrase into Electrum and send from there. Or use Electrum to sweep your coins.
Ava Chow
CC BY-SA 3.0
2017-11-06T05:52:37.243Z
2017-11-06T05:52:37.243Z
Ava Chow
<ul>
<li>Transfer from Legacy ⟶ SegWit: pay full fee (doesn't benefit from <a href="https://medium.com/segwit-co/what-is-behind-the-segwit-discount-8515a8d3bca9" rel="nofollow noreferrer">SegWit discount</a>)</li>
<li>Transfer from SegWit  ⟶ Legacy <em>or</em> SegWit: discounted.</li>
</ul>
<p><strong>Note:</strong> SegWit addresses can be <a href="https://github.com/bitcoin/bips/blob/master/bip-0173.mediawiki" rel="nofollow noreferrer">Bech32</a> <code>bc1...</code> or they can be <a href="https://github.com/bitcoin/bips/blob/master/bip-0141.mediawiki#p2wpkh-nested-in-bip16-p2sh" rel="nofollow noreferrer">nested</a> in a legacy P2SH <code>3...</code> address which are backwards-compatible (although less efficient). Many exchanges, wallets support the legacy &quot;nested&quot; form only.</p>

CC BY-SA 4.0
2017-11-06T12:14:31.983Z
2021-03-02T02:35:55.087Z
2021-03-02T02:35:55.087Z
Jonathan Cross
<p>Now that Electrum 3 supports Bech32 addresses for segwit, when sending coins to a legacy address are fees higher or cheaper?</p>

<segregated-witness><transaction-input><address-format><bech32-address>
How do transaction costs compare between Bech32 addresses and legacy Bitcoin addresses?
Patoshi パトシ
# How do transaction costs compare between Bech32 addresses and legacy Bitcoin addresses?

(Asked by: username_0 on 2017-11-06)

Now that Electrum 3 supports Bech32 addresses for segwit, when sending coins to a legacy address are fees higher or cheaper?

**Tags:** segregated-witness, transaction-input, address-format, bech32-address


---

## 2 answers

### Answer by username_2 on 2017-11-06. Score: 8 | Accepted answer

* Transfer from Legacy ⟶ SegWit: pay full fee (doesn't benefit from [SegWit discount](https://medium.com/segwit-co/what-is-behind-the-segwit-discount-8515a8d3bca9))
* Transfer from SegWit ⟶ Legacy *or* SegWit: discounted.

**Note:** SegWit addresses can be [Bech32](https://github.com/bitcoin/bips/blob/master/bip-0173.mediawiki) `bc1...` or they can be [nested](https://github.com/bitcoin/bips/blob/master/bip-0141.mediawiki#p2wpkh-nested-in-bip16-p2sh) in a legacy P2SH `3...` address which are backwards-compatible (although less efficient). Many exchanges, wallets support the legacy "nested" form only.


---

### Answer by username_1 on 2017-11-06. Score: 2

In general spending from a segwit output (i.e. "sending from" a segwit address) will be cheaper than spending a non-segwit output (i.e. "sending from" a non-segwit address). So yes, if you "send from" a bech32 address, it will be cheaper than "sending from" a P2PKH address.

> **Comments:**
> **username_0**: My coins are on mycellium now and I'm assuming I can't send these coins to a bc1 address. How do you suggest I move it into electrum? Do I just do a sweep?  
> **username_1**: Import your seed phrase into Electrum and send from there. Or use Electrum to sweep your coins.  

---

