forked from dashpay/dash
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Use Bech32m encoding for v1+ segwit addresses
This also includes updates to the Python test framework implementation, test vectors, and release notes.
- Loading branch information
Showing
9 changed files
with
375 additions
and
428 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -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). |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.