Taproot is just around the corner with a new encoding format for addresses. I already have a working version of btcutil with Bech32m, but it breaks the signature of bech32.Encode and bech32.EncodeFromBase256 with an additional encoding parameter and also returns an additional encoding value in the bech32.Decode and bech32.DecodeFromBase256, which is used to make sure that addresses use the correct encoding depending on the witness version.
If we can't break the current API, then we need to find a new name for these functions or create a new bech32m package. Any comments or suggestions welcome.
Taproot is just around the corner with a new encoding format for addresses. I already have a working version of btcutil with Bech32m, but it breaks the signature of
bech32.Encode
andbech32.EncodeFromBase256
with an additional encoding parameter and also returns an additional encoding value in thebech32.Decode
andbech32.DecodeFromBase256
, which is used to make sure that addresses use the correct encoding depending on the witness version.If we can't break the current API, then we need to find a new name for these functions or create a new
bech32m
package. Any comments or suggestions welcome.