diff options
author | Pieter Wuille <pieter@wuille.net> | 2021-01-05 13:36:42 -0800 |
---|---|---|
committer | Pieter Wuille <pieter@wuille.net> | 2021-03-27 12:09:44 -0700 |
commit | 593e206627f4fb789de70f55017f71b85d10754d (patch) | |
tree | 56f92f1f3b2475a26a130a9c065d3537316134ef /doc/release-notes-20861.md | |
parent | 8944aaa6d6ce55faa6224e288fe0a14dbbf5ca4f (diff) | |
download | bitcoin-593e206627f4fb789de70f55017f71b85d10754d.tar.xz |
Use Bech32m encoding for v1+ segwit addresses
This also includes updates to the Python test framework implementation,
test vectors, and release notes.
Github-Pull: #20861
Rebased-From: fe5e495c31de47b0ec732b943db11fe345d874af
Diffstat (limited to 'doc/release-notes-20861.md')
-rw-r--r-- | doc/release-notes-20861.md | 13 |
1 files changed, 13 insertions, 0 deletions
diff --git a/doc/release-notes-20861.md b/doc/release-notes-20861.md new file mode 100644 index 0000000000..5c68e4ab0c --- /dev/null +++ b/doc/release-notes-20861.md @@ -0,0 +1,13 @@ +Updated RPCs +------------ + +- Due to [BIP 350](https://github.com/bitcoin/bips/blob/master/bip-0350.mediawiki) + being implemented, behavior for all RPCs that accept addresses is changed when + a native witness version 1 (or higher) is passed. These now require a Bech32m + encoding instead of a Bech32 one, and Bech32m encoding will be used for such + addresses in RPC output as well. No version 1 addresses should be created + for mainnet until consensus rules are adopted that give them meaning + (e.g. through [BIP 341](https://github.com/bitcoin/bips/blob/master/bip-0341.mediawiki)). + Once that happens, Bech32m is expected to be used for them, so this shouldn't + affect any production systems, but may be observed on other networks where such + addresses already have meaning (like signet). |