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

user48884: 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.

user13440: 
Transfer from Legacy ⟶ SegWit: pay full fee (doesn't benefit from SegWit discount)
Transfer from SegWit  ⟶ Legacy or SegWit: discounted.

Note: SegWit addresses can be Bech32 bc1... or they can be nested in a legacy P2SH 3... address which are backwards-compatible (although less efficient). Many exchanges, wallets support the legacy "nested" form only.

3029: <p>Now that Electrum 3 supports Bech32 addresses for segwit, when sending coins to a legacy address are fees higher or cheaper?</p>
 48884: <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>
 13440: <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>
