user59657: According to github bitcoin/bips, BIP-173 is still a draft. And i saw today that Electrum wallet start using it.
Is this means that the specs for BIP-173 won't change in the future ? or the final version won't introduce breaking changes to the draft version ?
I just learned about Bech32 addresses this week and this gets me a little confused

user72128: Yes, they are. Bech32 addresses allow for native Segwit outputs, which offer higher efficiency and security than the legacy P2SH nested Segwit outputs. https://github.com/bitcoin/bips/blob/master/bip-0173.mediawiki#Reference_implementations has reference implementations in C, C++, JS, Go, Python, Haskell, Ruby, and Rust along with tests courteous of Pieter Wuille

59657: <p>According to github <a href="https://github.com/bitcoin/bips" rel="noreferrer">bitcoin/bips</a>, BIP-173 is still a draft. And i saw today that Electrum wallet start using it.</p>

<p>Is this means that the specs for BIP-173 won't change in the future ? or the final version won't introduce breaking changes to the draft version ?</p>

<p>I just learned about Bech32 addresses this week and this gets me a little confused</p>
 72128: <p>Yes, they are. Bech32 addresses allow for native Segwit outputs, which offer higher efficiency and security than the legacy P2SH nested Segwit outputs. <a href="https://github.com/bitcoin/bips/blob/master/bip-0173.mediawiki#Reference_implementations" rel="nofollow noreferrer">https://github.com/bitcoin/bips/blob/master/bip-0173.mediawiki#Reference_implementations</a> has reference implementations in C, C++, JS, Go, Python, Haskell, Ruby, and Rust along with tests courteous of <a href="https://bitcoin.stackexchange.com/users/208/pieter-wuille">Pieter Wuille</a></p>
